-
Notifications
You must be signed in to change notification settings - Fork 1
Using The Issue Trackers
BOSS v2.3.0 will change the BOSS Log's unrecognised plugin submission system, making it send submissions to the masterlist repository issue trackers here on GitHub instead of the Bugzilla issue tracker hosted by Dark Creations. The main advantages of this are that team members don't need to sign up for DC Bugzilla accounts, and the GitHub trackers are a lot simpler and in the same place as the masterlists. The Bugzilla tracker will be closed once v2.3.0 is released.
This wiki page gives an introduction to how to process plugin submissions in the issue trackers.
The issue trackers for each game are linked to below:
By default, all open issues are shown. All plugins submitted through the BOSS Log have an issue created for them by @boss-robot, which is an account created specifically for this purpose (WrinklyNinja has the account password, if any other admins would like it). You can search the issues for only those created by @boss-robot by entering author:boss-robot into the search bar at the top of the issue tracker's page.
Click on an issue to view its comment thread. The first time a plugin is submitted, an issue is created for it, but subsequent submissions are added as comments to the existing issue. To help reduce spam, duplicate comments are not added.
Check the comments for any useful information or links submitted, and add the plugin to the masterlist. When committing the addition to the repository, include the issue number (given next to the title) in the commit message, and GitHub will automatically link the commit to the issue and vice-versa. If you don't include the issue number in the commit, add a comment to the issue's thread containing the commit SHA (the long string of numbers and letters, you can copy/paste this). The issue can then be closed using the button next to the green "Comment" button.