-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create docs issue fourms #299
Conversation
I don't think we need feature and bug issue templates here do we? Seems a bit weird imo to have them on the docs repo |
Idk, the issue said most or all, so I took out the one's the definitely aren't needed for the docs website, these two felt a bit unneeded but I thought maybe they might have a use |
Would be worth somebody else chiming in with their opinion from Momentum, but I don't feel they're really required in the docs repo personally |
Could maybe update them to "new / update / deletion" or something |
Oh that's a good idea i'll do that |
Alright I did that, three new labels to add: "creation", "deletion", and "update" in place of the standard "documentation" label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quite often we'll have issues revolving around a specific area (internal merge request) which adds, changes, and removes documentation all at once (movement refactor was a good example). So I think we should consolidate all those into 1 form of 'Documentation'.
We do however need feature and bug submissions for the website itself. Eg. Adding the ability to display default/min/max values from metadata was a feature, and fixing broken links was a bug. Neither of those related were actual documentation.
Good points by brae. Looking at the existing issue labels we have now I'd suggest something like:
|
Resolves #268