Document the steps for creating a new julia-release-1-dot-N pipeline after a new release-1.N branch is made on JuliaLang/julia
#248
Conversation
|
It sure would be nice if we could write a Julia script that takes in a Buildkite token and the value of |
| 14. In the left-hand side, under "Pipeline Settings", click on "GitHub". Then, in the "Branch Limiting" section, do the following actions: | ||
| - Step i: For "Branch Filter Pattern", enter the following text: `release-1.9 v1.9.*` | ||
| - Step ii: Click on the green "Save Branch Limiting" button. | ||
| 15. You are still on the "Pipeline Settings ⟶ GitHub" page. In the "GitHub Settings" section, do the following actions: |
There was a problem hiding this comment.
I'm thinking for things like this, perhaps a picture is easier?
There was a problem hiding this comment.
Yeah.
I'm going to merge this just to get something in (currently we have nothing on main), but we should make follow-up PRs to add some screenshots.
DilumAluthge
force-pushed
the
dpa/creating-new-pipeline
branch
from
08edb5d
to
216542a
Compare
|
Note to self: additional things that I need to add here: https://buildkite.com/julialang/julia-release-1-dot-9/settings —> General —> Default Branch Needs to be release-1.9 Also: Also: |
DilumAluthge
force-pushed
the
dpa/creating-new-pipeline
branch
from
216542a
to
e9f3dea
Compare
…e after a new `release-1.N` branch is made on JuliaLang/julia
DilumAluthge
force-pushed
the
dpa/creating-new-pipeline
branch
from
e9f3dea
to
c6a3435
Compare
Fixes #43