golang

Expected Behavior

Current Behavior

Possible Solution

It would be good if Gitea offered support for the new citation file format, cf. https://citation-file-format.github.io/ and https://blog.front-matter.io/mfenner/step-forward-for-software-citation

This is intended to allow scientists to cite software repositories. I can imagine an implementation similar to Github: Similar to the buttons for forks and downloads of repositories, there may be a new

Describe the bug

When I try to fork a repo and add a new remote, it doesn't add a new remote to my current repository.

gh version 1.4.0 (2020-12-17)

Expected vs actual behavior

I expect to see a fork remote added to my repository, but nothing is added.

Logs

❯ gh repo fork --clone=false --remote=true $(git remote get-url up)
- Forking someorg/somerepo...

GenMarkdownTreeCustom has a way to a header (filePrepender arg), however there is not a first class way to add a footer.

Today we allow the unsafe-eval and unsafe-inline CSP directives only when the server was compiled as a developer build:

https://github.com/mattermost/mattermost-server/blob/ddfa6e2436d62ad022206859729d943a66f4427f/web/handlers.go#L177-L187

Let’s key this off the ServiceSetings.EnableDeveloper mode instead. I'm in a situation where I'd love to be able to debug a plugin on a non-dev-bui

@benoittgt very kindly submitted a PR to fix some spacing issues in the markdown using gofmtmd.

It should be possible to automate this as part of the build script