Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-pages.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGrzegorz Bizon <grzegorz@gitlab.com>2020-06-17 16:07:20 +0300
committerGrzegorz Bizon <grzegorz@gitlab.com>2020-06-17 16:07:20 +0300
commit0099e7a37a6d396d81e97b05c961322128b63eeb (patch)
tree28cc120407869fda6202d82da9428d59fde53ac0
parent681018e62afd4d08e992521a6e1545d2621bf30d (diff)
parent72eb95e13e12088698248dfe895639b60718ee2e (diff)
Merge branch 'vshushlin-master-patch-13782' into 'master'v1.19.0
Add a hint for showing diff for release See merge request gitlab-org/gitlab-pages!296
-rw-r--r--.gitlab/issue_templates/release.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/release.md b/.gitlab/issue_templates/release.md
index 7adaa21c..f1551178 100644
--- a/.gitlab/issue_templates/release.md
+++ b/.gitlab/issue_templates/release.md
@@ -2,6 +2,11 @@
- [ ] Review the list of changes since the last release and fill below:
- [ ] **In the changelog**
- [ ] **Not in the changelog**
+
+ Hint:
+ ```
+ git --no-pager log --merges --pretty=oneline master...vX.Y.Z
+ ```
- Decide on the version number by reference to
the [Versioning](https://gitlab.com/gitlab-org/gitlab-pages/blob/master/PROCESS.md#versioning)
* Typically if you want to release code from current `master` branch you will update `MINOR` version, e.g. `1.12.0` -> `1.13.0`. In that case you **don't** need to create stable branch