-
Notifications
You must be signed in to change notification settings - Fork 3
Add option to control sync of draft PRs #190
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
base: main
Are you sure you want to change the base?
Conversation
Repository maintainers can specify True/False under Repo -> `sync_drafts` in `.github/hubcast.yml`. Once the Gitlab as a source forge PR is merged we can integrate this option.
alecbcs
left a comment
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 good to me pending bot functionality comments when not being synced.
|
I'll implement that right now, I have no idea why I wrote that comment considering it's been in for a few months 😅 |
|
No worries haha :) |
|
To avoid handling past comments when the status of a PR changes, we also have a couple alternatives:
|
|
I'd vote for the 1st option, but let's make it optional via a config. Some users might want to disable draft PRs and not get a message from Hubcast while others probably do want a place holder status check with a message. |
"skipped" for draft PRs where sync was skipped. Rewrote a bit of `set_check_status` to allow setting a title-only status check.
implemented in 71ffa0c |
Repository maintainers can specify True/False under Repo ->
sync_draftsin.github/hubcast.yml.Once the Gitlab as a source forge PR is merged we can integrate this option.