BigW Consortium Gitlab
don't set LATEST_TAG automatically in patch update guide As discussed in https://gitlab.com/gitlab-org/gitlab-ce/issues/2607, this removes the automatic setting of the LATEST_TAG variable in the update guide, because it could get set to rc versions. Instead, a command was added to list all tags, with the most recent one being on the end of the list. Also a note was added to prevent users from updating to new minor/major versions because the tag list includes all tags. [ci skip] See merge request !1510
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api | Loading commit data... | |
ci | Loading commit data... | |
customization | Loading commit data... | |
development | Loading commit data... | |
gitlab-basics | Loading commit data... | |
hooks | Loading commit data... | |
incoming_email | Loading commit data... | |
install | Loading commit data... | |
integration | Loading commit data... | |
legal | Loading commit data... | |
logs | Loading commit data... | |
markdown | Loading commit data... | |
migrate_ci_to_ce | Loading commit data... | |
operations | Loading commit data... | |
permissions | Loading commit data... | |
profile | Loading commit data... | |
project_services | Loading commit data... | |
public_access | Loading commit data... | |
raketasks | Loading commit data... | |
release | Loading commit data... | |
security | Loading commit data... | |
ssh | Loading commit data... | |
system_hooks | Loading commit data... | |
update | Loading commit data... | |
web_hooks | Loading commit data... | |
workflow | Loading commit data... | |
README.md | Loading commit data... |