Alexander Kurakin <[email protected]> writes: > Thanks for the to-Codeberg migration. > I appreciate it very much, > not least because of the non-fork (AGit) contributing approach > and my support for lightweight (and more open-source BTW) tools > (Forgejo/Gitea).
Thank you, that is nice to hear :) > There are some notes on our instructions. > > 1. [0] refer to the authorized clone URL: > `[email protected]:repo/gentoo.git`. > But cloning in such way is available for Gentoo developers only, right? > Should we mention the anonymous > (`https://anongit.gentoo.org/git/repo/gentoo.git`) clone URL? > > 2. [1] doesn’t have the clone URL/command. > > 3. What should `$topic`/$TOPIC` be, exactly? The branch name, the PR title, > else? > You can use my first PR there [2] to point out. The topic is an identifier for your PR. I typically just use the branch name, but it appears to be more or less free-form, see https://codeberg.org/gentoo/gentoo/pulls/38 for an interesting topic :) > 4. Are we able to set the PR’s content (description) just on push? > Yes, now I see some information at [3], but is it it worth to adopt it in [2]? Yes, the description can be set on push with -o description. If omitted, the default is to use the body text of the last commit in the PR. I would encourage people to find (or develop) tooling that makes it easier to fill in a description, and preferably tooling that uses the description template in .github. For example, if you use Emacs, there's app-emacs/agitjo that prompts for a PR description just before the push. It will even use a PR description template found {.github,.forgejo,.gitea}/pull_request_template.md. I opened https://codeberg.org/gentoo/gentoo/pulls/281 using agitjo. > 5 Should [4] have TOC (the inner pages list)? Thanks for the feedback re documentation, I've passed it along (I cannot edit the project wiki pages myself). All the best, -- Thomas
