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.

Some plugins render their components in the team sidebar, but the sidebar is only visible when the user is a member of more than one team. It would be useful to be able to configure the system to always show the team sidebar, so that users with only one team membership can use the plugin properly.

If you're interested please comment here and come [join our "Contributors" community channel](

@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