Skip to content
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

sync: update CI config files #1082

Merged
merged 16 commits into from
Apr 30, 2021
Merged

sync: update CI config files #1082

merged 16 commits into from
Apr 30, 2021

Conversation

web3-bot
Copy link
Collaborator

Syncing to commit protocol/.github@137ffc6.

@Stebalien Stebalien force-pushed the web3-bot/sync branch 2 times, most recently from eaf2871 to cfdf87e Compare April 29, 2021 23:30
@github-actions github-actions bot merged commit 142d237 into master Apr 30, 2021
@github-actions github-actions bot deleted the web3-bot/sync branch April 30, 2021 02:33
@Stebalien Stebalien restored the web3-bot/sync branch April 30, 2021 03:34
@Stebalien Stebalien deleted the web3-bot/sync branch April 30, 2021 03:34
@Stebalien
Copy link
Member

Hm. So... that's one problem with the auto-merge.

@marten-seemann
Copy link
Contributor

Hm. So... that's one problem with the auto-merge.

@Stebalien We could change the auto-merge logic such that it only triggers if all commits in a PR have web3-bot as commit author (or committer?). WDYT?

@Stebalien
Copy link
Member

Yeah, that would be really nice. Commit author probably makes sense, rebase should be fine.

NOTE: I'm slightly concerned about it allowing contributors to bypass merge policies. I'm wondering if we should protect the web3-bot branches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants