-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add a component path to every component data #325
Comments
@pmi done, close? |
Hm, it says that it's archived in NextJS project, and should've been closed by merge of the PR |
@alansemenov Is that correct that it is not closed after PR is merged ? |
I was wondering about this too. We probably don't want auto close as this is done after every sprint |
Unfortunately, it's not (yet) automatic in Github projects :(. The one who merges a PR, should change status (or drag the issue) to "Done". You can close the issue as well, it will still remain in "Done". After sprint review we'll archive everything in "Done", so that these issues disappear from the dashboard. |
Correction: the workflow was not entirely correct in the project. I've now changed it so that whenever an issue is closed (with the "Close" button), it will be automatically moved to "Done". So, whoever merges a PR, should close the issue. It will be moved to "Done", then manually archived after sprint review. |
No description provided.
The text was updated successfully, but these errors were encountered: