-
Notifications
You must be signed in to change notification settings - Fork 236
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
Feature Request: 'Latest' release branch creating as part of release process #259
Comments
I'd like to get Travis to do this, I've had a go over here. It should check out the tag matching the version number in the VERSION.txt file, use this tag to create a new branch "latest-release" and push this to GitHub. |
That sounds great! |
Sounds like you have your heads around this now .... thanks |
Well, that look a little longer than expected. @paulmsmith can you please confirm that this fixes this issue and i'll raise a separate issue for updating the documentation. |
Hey Gemma, been getting the emails today! Way to go for persistence! Fiddly things like that are stressful but feel great when solved. I will double check when back at my desk. If you can raise that ticket I'll get that tiny piece of this done. |
Pull Request made and referenced your ticket @gemmaleigh: 271 |
My documentation branch (awaiting merge) grabs the url to the zip of the latest release, avoiding the need for novice users to visit github at all. You can see the branch deployed here. |
@edwardhorsford That's cool. I think that's an a nice update to the manual way of updating or getting the latest version. My documentation is around using git to pull down and merge the latest version via the command line. |
Ah sorry @paulmsmith, a misunderstanding on my part. Sounds good then! |
# 0.19.2 - Increase skiplink colour contrast ([PR #263](alphagov/govuk_template#263)) # 0.19.1 - Have focus outline appear outside of element rather than covering it in Safari and Chrome ([PR #259](alphagov/govuk_template#259))
There is a need for users to be able to easily get the 'latest' version (release) of the Prototyping Kit. Experienced users of Git will know about releases and know to checkout 'tags' but most people won't (and probably don't need to) know that.
In the updating documentation a git branch is required to be able to quickly target the latest version of the kit and merge it into their fork.
Proposal. Use something like Release Event to automatically create/update the 'latest' branch. (Hat tip @alextea)
Thoughts. @gemmaleigh ?
The text was updated successfully, but these errors were encountered: