You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user wants to know what changes we have in a release, it should be a release page with all the details.
Describe Ideal Solution
Now the workflow is:
build an image
create a tag
The ideal workflow should be:
create a PR
merge it to master
do the same with all the PRs you need
then release drafter will create the draft for all the PRs
publish the release
the previous action triggers the image build/push with the desired version
Keep in mind we have to figure out how to maintain two different image versions (aka two different releases).
This can be done with version branches. E.g. for versions 1.2.7-0.1.1 and 1.3.5-0.0.1, being the later the main one:
from master we build the latter one
from release/1.2.7 we build the former one
Another possibility is not to work with master and instead have all release branches and work from there:
release/1.2.7
release/1.3.5
I don't know how release drafter works, so it has to be researched.
exequielrafaela
changed the title
Enhancement | Add release notes and readme in DockerHub
Enhancement | Add release + notes at GH repo and auto-sync readme (if possible) in DockerHub
Jan 26, 2023
@juanmatias this PR (#56) intends to cover add/update a readme in Docker Hub with the needed release information via a highlighted link. Still pending the automated releases with comments which should be migrated / handled from CircleCI to GH Actions:
Build, test, push image to dockerhub
Release drafter GH action implementation (same as we do in all other repos).
Describe the Enhancement
Add a way to create releases and release notes in the repo and add/update a readme in Docker Hub.
Expected Behavior
To have up-to-date notes.
If possible keep the standard approach and format that's being used across all binbash GH org repos => https://github.com/binbashar/leverage/releases with https://github.com/binbashar/leverage/blob/master/.github/release-drafter.yml
Use Case
When a user wants to know what changes we have in a release, it should be a release page with all the details.
Describe Ideal Solution
Now the workflow is:
The ideal workflow should be:
Keep in mind we have to figure out how to maintain two different image versions (aka two different releases).
This can be done with version branches. E.g. for versions
1.2.7-0.1.1
and1.3.5-0.0.1
, being the later the main one:master
we build the latter onerelease/1.2.7
we build the former oneAnother possibility is not to work with
master
and instead have all release branches and work from there:release/1.2.7
release/1.3.5
I don't know how release drafter works, so it has to be researched.
Alternatives Considered
n/a
Additional Context
n/a
@diego-ojeda-binbash @exequielrafaela @angelofenoglio
The text was updated successfully, but these errors were encountered: