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.

Sign up for GitHub

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

Jump to bottom

Changes needed for new branch structure #1092

Open
Tracked by #1094
goneall opened this issue Aug 26, 2024 · 0 comments
Open
Tracked by #1094

Changes needed for new branch structure #1092

goneall opened this issue Aug 26, 2024 · 0 comments
Assignees
@bact
Labels
ci Dev workflow and repo management doc improvement Area where the project documentation needs improvement.
Milestone
3.0.1

Comments

@goneall
Copy link
Member

goneall commented Aug 26, 2024 •
edited
Loading

From the 2024-08-14 tech discussion on spec publishing and the previous discussion on translations on 2024-06-11, we agreed to rename the "under development" branch to main. This will likely break the CI.

We should create a PR for CI updates, then rename the branch before merging.

We also need to document exactly what the changes are.

We also update README and/or CONTRIBUTING file
@goneall goneall added this to the 3.0.1 milestone Aug 26, 2024
@bact bact mentioned this issue Aug 27, 2024
Closed
@goneall goneall changed the title Update CI for new branch structure Changes needed for new branch structure Aug 27, 2024
@goneall goneall mentioned this issue Aug 27, 2024
Open
11 tasks
@bact bact mentioned this issue Sep 2, 2024
Merged
6 tasks
@bact bact added doc improvement Area where the project documentation needs improvement. ci Dev workflow and repo management labels Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bact bact

Labels
ci Dev workflow and repo management doc improvement Area where the project documentation needs improvement.
Projects
None yet
Milestone
3.0.1
Development

No branches or pull requests
2 participants
@bact @goneall