You need to create PR to complete your part. Then reviewers will check the PR request and give you feedback (approve and merge or ask you to revise and improve if anything not sufficient).
The Pagure PR guide was brought back to life only on 22 April. I was contemplating to add images, but pushed the text first. Please let me know how you get on.
Maybe, we need a separate thread for Docs contributor onboarding, something like that.
Check New Pull Request and you will see source branch and target branch. You’re close to the finish line.
I see PR made. Looks good to me. I can’t merge PR because I don’t have write access to the repo to merge. Wait for admin group to see your PR and get back to you.
Maybe a requirement of all docs repos should be that members of the core docs team should have write access to them? Similar to “proven packagers” to ensure that minor changes don’t have to wait for individual teams to be merged/fixed?
As the policy notes, these powers are only rarely used, but they’re very useful.
Thanks @ankursinha , could you split contents related to Pagure PR as a new thread?
Maybe a requirement of all docs repos should be that members of the core docs team should have write access to them? Similar to “proven packagers” to ensure that minor changes don’t have to wait for individual teams to be merged/fixed?
I think the workflow is there within reason and expected behavior. It’s fine for me. I just let Sampson know the ball is on workstation team.