Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add
prebuildDefaultBranchOnly
setting – EXP-574 #18716Add
prebuildDefaultBranchOnly
setting – EXP-574 #18716Changes from 12 commits
8012bc7
1f34982
5ce8104
af8e407
f17e190
4c814ee
9a8e9df
623b5a5
d53d9eb
9aac05a
fc3e77d
6ec7dae
31a1409
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
suggestion: Not sure if this is the most relevant line, but regarding the indentation, this
ml-6
andmt-4
.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.
issue(non-blocking): Not sure if we need the example branch name here, but we can remove at any time later.
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.
can this be removed?
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.
here (similar to enablePrebuilds above) we introduce an optional property where
undefined
meanstrue
. I think that is confusing. Can we make itprebuildAllBranches?: boolean
or as we are going to allow a pattern already use a pattern internally and make it*
?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.
Alternatively, introduce a non-boolean property (i.e. the strategy thing below).
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.
I would like to remove the optional from
prebuildAllBranches
. This was a concern of rolling out to Gitpod Cloud.Once we agree on a data migration path, we can remove the
?
.I'm also OK with using constant to represent those states, e.g.
all-branches
,default-branch
,matched-branches
. Actually this would be even simpler, as we are using a<select>
in frontend, which maps to a tuple of boolean to represents this state.