-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[GitHub.com only] Prebuilds no longer triggering if gitpod.yml uses a 'before' task without an 'init' #10336
Comments
Here is an example where the prebuild stopeed working |
Ah, indeed, sorry that was indeed my fault. 😬 The previous and current My change actually "aligned" the I'm happy to re-introduce EDIT: See PR (feel free to aprove or close it) |
@jldec @jankeromnes While aligning with other Git hosters is nice please be aware that GitHub is at least 90% of our users. Did you think about reversing this, and making the "before" behavior the default for all hosters? (Not pushing for this, just want to make sure we thought about this from all perspectives. 👍 ) |
Good point. 👍
I think this would make sense, and have implemented that here: #10352 |
The following .gitpod.yml used to trigger prebuilds on each commit (on GitHub only) but as of 21d3f00 it no longer does.
Since the old behavior was somewhat unexpected, and GitHub-specific, and atypical (the standard way to configure a prebuild is with
init
) the proposal for this issue is NOT to fix this, but rather to clarify the recommended use ofinit
in our docs.The text was updated successfully, but these errors were encountered: