Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-shell
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-shell
Commits
f618d479
Commit
f618d479
authored
Mar 29, 2017
by
Sean McGivern
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Explain how to release a new version
parent
199e2d62
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
0 deletions
+14
-0
README.md
README.md
+14
-0
No files found.
README.md
View file @
f618d479
...
@@ -131,3 +131,17 @@ Remove all keys from authorized_keys file:
...
@@ -131,3 +131,17 @@ Remove all keys from authorized_keys file:
## Git LFS remark
## Git LFS remark
Starting with GitLab 8.12, GitLab supports Git LFS authentication through ssh.
Starting with GitLab 8.12, GitLab supports Git LFS authentication through ssh.
## Releasing a new version
GitLab Shell is versioned by git tags, and the version used by the Rails
application is stored in
[
`GITLAB_SHELL_VERSION`
](
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/GITLAB_SHELL_VERSION
)
.
To release a new version of GitLab Shell and have that version available to the
Rails application:
1.
Update the
[
`CHANGELOG`
](
CHANGELOG
)
and
[
`VERSION`
](
VERSION
)
files.
2.
Add a new git tag.
3.
Update
`GITLAB_SHELL_VERSION`
in the Rails application. (Note: this can be
done as a separate MR to that, or in and MR that will make use of the latest
GitLab Shell changes.)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment