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

Separate branches for dev and for production server #288

Open
tmushayahama opened this issue Nov 3, 2022 · 3 comments
Open

Separate branches for dev and for production server #288

tmushayahama opened this issue Nov 3, 2022 · 3 comments

Comments

@tmushayahama
Copy link

tmushayahama commented Nov 3, 2022 •
edited
Loading

Just to make it consistence with noctua dev server vs noctua production. Separate branches for dev and for production server for testing purposes and playgrounds

What are your thoughts

@kltm @balhoff @vanaukenk @ukemi
@kltm
Copy link
Member

kltm commented Nov 3, 2022

Why not just use a branch? If I'm understanding correctly, I think spreading code for the same codebase in different states across different repos would get confusing.

@tmushayahama
Copy link
Author

@kltm I meant a branch, like dev and master just like the noctua workflow

@tmushayahama tmushayahama changed the title Separate repos for dev and for production server Separate branches for dev and for production server Nov 3, 2022
@kltm
Copy link
Member

kltm commented Nov 3, 2022

Sounds fine to me, although I'm not sure of the flow. We do the same things with noctua-models, minerva, noctua, etc.

@kltm kltm mentioned this issue Dec 12, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tmushayahama @kltm