-
Notifications
You must be signed in to change notification settings - Fork 1
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 a reproducible workflow strategy compatible with soft-fork #19
Conversation
@siddharth-krishna @daniel-rdt @yerbol-akhmetov As discussed last week, here is the PR. Your feedback is welcome ! |
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.
Thanks, Thomas! This is a nice idea. I've left some minor comments. I'm also wondering if the first paragraph should say something about the soft fork strategy and link to the handbook?
@siddharth-krishna I've added a new paragraph in the README. |
Co-authored-by: Siddharth Krishna <siddharth-krishna@users.noreply.github.com>
Co-authored-by: Siddharth Krishna <siddharth-krishna@users.noreply.github.com>
ccada57
to
3b72e5c
Compare
Closes open-energy-transition/cookiecutter-project#2.
Changes proposed in this Pull Request
To make the soft-fork strategy compatible with the concepts of the
cookiecutter
, it is suggested that the necessary files be included in the main repository. With this structure it should be easy to kick out projects as soft-forks.Checklist
envs/environment.yaml
.config/config.default.yaml
.doc/configtables/*.csv
.doc/data_sources.rst
.doc/release_notes.rst
is added.