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

Investigate the use of a dev branch to not merge often to the stable main #486

Open
anenadic opened this issue Jan 24, 2025 · 1 comment
Open

Investigate the use of a dev branch to not merge often to the stable main #486

anenadic opened this issue Jan 24, 2025 · 1 comment
Assignees
@tobyhodges
Labels
admin Issues related to administration of the repository/project/training
Milestone
2025 Release

Comments

@anenadic
Copy link
Collaborator

anenadic commented Jan 24, 2025 •
edited
Loading

  • talk to Rob Davey about having a separate site build from the dev branch (e.g. using Netlify) and we could teach from it if we wanted to
@anenadic anenadic added this to the 2025 Release milestone Jan 24, 2025
@sstevens2 sstevens2 added the admin Issues related to administration of the repository/project/training label Jan 24, 2025
@anenadic
Copy link
Collaborator Author

anenadic commented Feb 28, 2025 •
edited
Loading

Sarah and Aleks discussed this at the maintainers meeting 2025-02-28 and decided that the scope of changes do not warrant a dev branch at this time. We will wait to confirm with @tobyhodges before closing this issue.

Related to #188 - should close both issue at the same time.

@anenadic anenadic mentioned this issue Feb 28, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tobyhodges tobyhodges

Labels
admin Issues related to administration of the repository/project/training
Projects
None yet
Milestone
2025 Release
Development

No branches or pull requests
3 participants
@anenadic @sstevens2 @tobyhodges