-
Notifications
You must be signed in to change notification settings - Fork 183
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
No resolved status #99
Comments
@caleuanhopkins When you close a issue, the statuspage generator will show it as resolved. |
@marceldiass tried that but the issue closes in Github and disappears from statuspage after running the update command. The page just displays the "no issues in the last 90 days" message. https://github.com/caleuanhopkins/binkystatus/issues?q=is%3Aissue+is%3Aclosed I have no resolved label in the issues section too so there's no label to attach to the issue when it's closed |
This happens to me as well. It disappears from historical once you close an issue. EDIT: something weird happened. I opened a new issue, (I only had 1 closed issue at this point) and I ran update. Now both the old resolved issue and the new issue showed up! EDIT2: Another weird thing I noticed. Once you update an issue with a comment, you have to update twice for that comment to show up. The second time around it'll say 'nothing to commit' although it commits anyway. |
@MightyRevenge yeah I now have same thing happen. My old issues now appear as "Resolved" but have to run the update command twice |
This is happening to me, too. I tried manually creating a "resolved" label first because I couldn't figure out how to get that to show up, but when I did I got the error message found in #96. Then I tried closing the issue and it disappeared from the list and it just now says "no issues in the last 90 days" |
I opened PR with the fix #149 |
I installed the system yesterday, everything is running fine but I have no label for "resolved" status. Is there any way I can add this status in manually?
The text was updated successfully, but these errors were encountered: