https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37539
--- Comment #5 from David Nind <[email protected]> --- (In reply to Rudolf Byker from comment #4) > Yay, merge requests! It's a much easier workflow, IMO. I will open the MR. > How do I close or reject this bug? We use Bugzilla to track documentation changes, so leaving this bug is fine: - for changes to the Koha code, the status of a bug is changed to "Needs documenting" once it is pushed to the last maintenance release it will go in (release maintainers do this) OR - a bug in the documentation component, we use the "Needs documenting" status (although I can't seem to change it to that for this one, so I wouldn't worry about that). Once you have made the merge request, in Bugzilla: 1. Add your name to the "Documentation contact" Bugzilla field 2. Add a link to your merge request for the "Documentation submission" Bugzilla field 3. The documentation team manager will review - there may be comments back and forwards until they are happy. 4. Once the merge request is approved, it will be incorporated into the manual with continuous build process (can take an hour or so, depending). 5. Once it is merged, you can change the bug to "FIXED CLOSED" For an occasional or one off change, using the GitLab interface is probably easier https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual#Editing_the_manual_-_using_the_GitLab_web_interface (unless you are more familiar with git and are happy to work on it locally). Post in the Documentation channel in the chat if you have questions. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
