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

Make the bot go through the normal branch-green-merge process #10

Open
msprotz opened this issue Dec 7, 2016 · 0 comments
Open

Make the bot go through the normal branch-green-merge process #10

msprotz opened this issue Dec 7, 2016 · 0 comments
Labels

Comments

@msprotz
Copy link
Member

msprotz commented Dec 7, 2016

Right now the hint auto-regeneration thing (target: fstar-nightly) relies on dzomo, the bot, being administrator on the F* project because of the branch restriction.

  • This is unfortunate and weakens security.
  • If we give the bot just write access, then the bot will have to push to a branch, get a green, and merge into master.
  • This can be achieved by putting MERGEME in the commit message, then pushing to branch dzomo. Then, the next job (target: fstar-ci), upon getting a green on the branch, will try to merge it.
  • However, how can we delay the merge & push of the branch to master, long enough so that VSTS gives that goddamn green to GitHub?

nohup merge_branch

where

merge_branch () {
  sleep 60 # long enough for GitHub to receive a green
}

?

I doubt that this will work

@msprotz msprotz changed the title VSTS: post-commit hook? Make the bot go through the normal branch-green-merge process Dec 8, 2016
@vkanne-msft vkanne-msft added the P3 label Dec 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants