-
Notifications
You must be signed in to change notification settings - Fork 210
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
Fallback #120
Fallback #120
Conversation
- Actual revert not yet implemented
I mean it fits the name chaos. But the thought of adding a commit revert wind up clock makes me uncomfortable. However I am interested in the idea of being able to revert a commit via api |
@MINIMAN10000 I can't say I'd ever want it to happen myself, but I like the idea of the threat being there 😛 |
- Update date variable to reflect that deltatime does not have an hour attribute
(updated description & title) |
github_api/repos.py
Outdated
if(len(data) > 0) | ||
# return previous commit sha if it exists | ||
if(len(data) >= 1) | ||
data[0]['last_commit_sha'] = |
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.
Looks like a mistake
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 right, thanks for spotting that. I thought I'd removed it.
🙆♀️ PR passed with a vote of 7 for and 3 against, with a weighted total of 4.0 and a threshold of 3.6. See merge-commit bffbc96 for more details. |
This has become a little more ominous than the original intention, which was to revert the most recent PR if no PR has been approved in the last 24 hours. I found that this was not something that could be done via the API, and so I propose a new consequence for inaction:
If no PR has been approved in the last 24 hours, Chaos randomly chooses a PR with no conflicts, and merges it in spite of the current vote.
The main purpose of this is to encourage progress (I'm afraid of the result of this PR myself), and of course introduce some chaos. This PR ensures that there will always be a discussion to be had.
Extra bonus: this PR includes a little class for handling commit objects, might come in handy for others.