Commit 115bbd8a authored by Robert Speicher's avatar Robert Speicher

Merge remote-tracking branch 'ce/8-2-stable' into 8-2-stable-ee

parents a9a303a2 0df53400
8.2.0.rc2-ee 8.2.0.rc2-ee
\ No newline at end of file
...@@ -32,6 +32,8 @@ class DroneCiService < CiService ...@@ -32,6 +32,8 @@ class DroneCiService < CiService
def compose_service_hook def compose_service_hook
hook = service_hook || build_service_hook hook = service_hook || build_service_hook
# If using a service template, project may not be available
hook.url = [drone_url, "/api/hook", "?owner=#{project.namespace.path}", "&name=#{project.path}", "&access_token=#{token}"].join if project
hook.enable_ssl_verification = enable_ssl_verification hook.enable_ssl_verification = enable_ssl_verification
hook.save hook.save
end end
......
...@@ -10,6 +10,7 @@ ...@@ -10,6 +10,7 @@
- [Repositories](repositories.md) - [Repositories](repositories.md)
- [Repository Files](repository_files.md) - [Repository Files](repository_files.md)
- [Commits](commits.md) - [Commits](commits.md)
- [Tags](tags.md)
- [Branches](branches.md) - [Branches](branches.md)
- [Merge Requests](merge_requests.md) - [Merge Requests](merge_requests.md)
- [Issues](issues.md) - [Issues](issues.md)
......
...@@ -254,13 +254,12 @@ Developing software happen in small messy steps and it is OK to have your histor ...@@ -254,13 +254,12 @@ Developing software happen in small messy steps and it is OK to have your histor
You can use tools to view the network graphs of commits and understand the messy history that created your code. You can use tools to view the network graphs of commits and understand the messy history that created your code.
If you rebase code the history is incorrect, and there is no way for tools to remedy this because they can't deal with changing commit identifiers. If you rebase code the history is incorrect, and there is no way for tools to remedy this because they can't deal with changing commit identifiers.
## Voting on merge requests ## Award emojis on issues and merge requests
![Voting slider in GitLab](voting_slider.png) ![Emoji bar in GitLab](award_emoji.png)
It is common to voice approval or disapproval by using +1 or -1 emoticons. It is common to voice approval or disapproval by using +1 or -1. In GitLab you
In GitLab the +1 and -1 are aggregated and shown at the top of the merge request. can use emojis to give a virtual high five on issues and merge requests.
As a rule of thumb anything that doesn't have two times more +1's than -1's is suspect and should not be merged yet.
## Pushing and removing branches ## Pushing and removing branches
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment