| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
If HTTPS was used for 'project_url', an error was raised because a HTTP
connection was established to the default HTTPS port.
The code has been corrected and simplified by using HTTParty.
Additionally, the request now is made directly to the 'project_url'
instead of the extracted root path.
|
|
|
|
Closes #772
|
|
|
|
|
|
Remove duplicate settings for default_url_options
Closes #2269
See merge request !1797
|
|
|
|
When notify is set to true send messages will trigger a notification for
all room members.
Color changes the background color of the message.
|
|
Closes internal https://dev.gitlab.org/gitlab/gitlabhq/issues/2269
|
|
Fix broken link in jira service
|
|
|
|
Prevent arbitary local repos from being imported.
Fixes gitlab/gitlab-ee#263.
See merge request !1763
|
|
Fix persistent XSS vulnerability around profile website URLs.
Fixes gitlab/gitlab-ee#268
See merge request !1761
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Send EmailsOnPush email when branch or tag is created or deleted.
Addresses #1951, #1957 and #1925.
See merge request !1709
|
|
|
|
|
|
|
|
Add support for external wikis
## What does this MR do?
This MR adds the possibility to replace the link to the internal wiki of gitlab with a custom link.
Currently this is realised as a service.
## What Use Case does this MR solve?
In my Company we already have a wiki System (Confluence).
We have a policy to use the existing wiki, so we can't switch to the internal wiki Gitlab provides.
This currently only leaves us two choices:
1. Disable the gitlab wiki. That means we completly loose the connection between wiki and code from the gitlab ui.
2. Create a simple wiki page with a link to our external wiki and hope that no one uses the internal one.
Both solutions are not really good.
So what can be done to improve the situation while making it as easy as possible for new developers to access both, wiki and gitlab?
Replacing the wiki link kinda like the JIRA integration replaces the issues link looks like a good first step to me. :)
This can probably be extended later to completly prevent access to the internal wiki (currently that's still possible if you know the link) or maybe to check if the link really points to a wiki.
## Screenshot:
See merge request !291
|
|
Make Irker service check supported_events
63178a9509f72eb7adf1c73c2fc6dc1ec0a1ea42 added the supported_events check for services. Since f84b7eef3f969a65d0930c9d62b6968b2ae70f12 was just added, we should adjust it accordingly.
See merge request !367
|
|
|
|
|
|
Properly move over `issues_tracker_id` from old custom issue tracker URLs.
Addresses https://gitlab.com/gitlab-org/gitlab-ce/issues/1124.
cc @marin Regression in 7.8.0.
See merge request !1670
|
|
|
|
|
|
Conflicts:
app/controllers/projects/services_controller.rb
app/models/project_services/emails_on_push_service.rb
|
|
Normalize output to use:
- User name instead of username
- Include first line of title in message description
- Link to "Issue #X" instead of "#X"
|
|
Supports four different event types all bundled under the "note" event type:
- comments on a commit
- comments on an issue
- comments on a merge request
- comments on a code snippet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1) Adds a DB migration for all services to toggle on push, issue, and merge events.
2) Upon an issue or merge request event, fire service hooks.
3) Slack service supports custom messages for each of these events. Other services
not supported at the moment.
4) Label merge request hooks with their corresponding actions.
|
|
Fix for TeamCity buildQueue REST API build/@branchName.
|
|
Aorimn-add-irker-service
Conflicts:
app/controllers/projects/services_controller.rb
|
