We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We don't have at the moment any release, but we can tag the commit used for the past ODW and continue doing so for future workshops.
This way it will be easier to check out the specific repo for a given year.
Tag could be v2024, v2025, etc, or v7.0, v8.0 etc. Tagging by the year it was made or the ODW number.
v2024
v2025
v7.0
v8.0
The text was updated successfully, but these errors were encountered:
It seems that commit 113d53c is the one used for ODW #7 (2024).
Sorry, something went wrong.
Hi Martin,
Yes, that was one of the goal of this "permanent repository". I did not do it yet because in my mind, this repository is still experimental.
So my idea was to wait if this organization is successful for ODW 2025 and then tag (perhaps retrospectively).
Also as there is a repository for ODW 2024 maybe it would confuse people if we create this tag here.
That's my 2 cents.
No branches or pull requests
We don't have at the moment any release, but we can tag the commit used for the past ODW and continue doing so for future workshops.
This way it will be easier to check out the specific repo for a given year.
Tag could be
v2024
,v2025
, etc, orv7.0
,v8.0
etc. Tagging by the year it was made or the ODW number.The text was updated successfully, but these errors were encountered: