-
Notifications
You must be signed in to change notification settings - Fork 0
docs: 📝 describe in more detail how releases work #255
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
Conversation
signekb
left a comment
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.
Some suggestions ✏️ :
CHANGELOG.md
Outdated
| workshop content that we publish automatically to Zenodo for easier | ||
| discovery, archival, and citation purposes. We use |
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.
This made me think whether we should only publish to Zenodo after a workshop has been completed (so once/twice a year)?
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.
That's too complicated. We'd have to turn the synching on and off manually when we want it uploaded. Which isn't exactly a nice workflow.
Co-authored-by: Signe Kirk Brødbæk <40836345+signekb@users.noreply.github.com>
Description
The original one was too much targeted to software, so I expanded this description.
Checklist
just run-all