Commit fb81d69c authored by GitLab Bot's avatar GitLab Bot

Automatic merge of gitlab-org/gitlab master

parents c80fb62c 2e06152d
......@@ -626,7 +626,7 @@ lib/gitlab/checks/** @proglottis @toon @zj-gitlab
/doc/raketasks/x509_signatures.md @aqualls
/doc/security/ @eread
/doc/ssh/index.md @eread
/doc/subscriptions/ @sselhorn
/doc/subscriptions/ @fneill
/doc/system_hooks/system_hooks.md @kpaizee
/doc/topics/authentication/index.md @eread
/doc/topics/autodevops/customize.md @marcia
......@@ -791,5 +791,5 @@ lib/gitlab/checks/** @proglottis @toon @zj-gitlab
/doc/user/snippets.md @aqualls
/doc/user/tasks.md @msedlakjakubowski
/doc/user/todos.md @msedlakjakubowski
/doc/user/usage_quotas.md @sselhorn
/doc/user/usage_quotas.md @fneill
/doc/user/workspace/index.md @fneill
---
stage: Enablement
group: Distribution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
redirect_to: 'index.md'
remove_date: '2022-05-24'
---
# Namespaces **(FREE SELF)**
This document was moved to [another location](index.md).
This Rake task enables [namespaces](../user/group/index.md#namespaces) for projects.
## Enable usernames and namespaces for user projects
This command enables the namespaces feature. It moves every project in its
namespace folder.
The **repository location changes as part of this task**, so you must **update all your Git URLs** to
point to the new location.
To change your username:
1. In the top-right corner, select your avatar.
1. Select **Edit profile**.
1. On the left sidebar, select **Account**.
1. In the **Change username** section, type the new username.
1. Select **Update username**.
For example:
- Old path: `git@example.org:myrepo.git`.
- New path: `git@example.org:username/myrepo.git` or `git@example.org:groupname/myrepo.git`.
```shell
bundle exec rake gitlab:enable_namespaces RAILS_ENV=production
```
<!-- This redirect file can be deleted after <2022-05-24>. -->
<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page -->
......@@ -75,4 +75,9 @@ Access our [permissions](../../permissions.md) page for more information.
When you [add a linked issue](#add-a-linked-issue), you can show that it **blocks** or
**is blocked by** another issue.
Issues that block other issues have an icon (**{issue-block}**) shown in the issue lists and [boards](../issue_board.md).
Issues that block other issues have an icon (**{issue-block}**) next to their title, shown in the
issue lists and [boards](../issue_board.md).
The icon disappears when the blocking issue is closed or their relationship is changed or
[removed](#remove-a-linked-issue).
If you try to close a blocked issue using the "Close issue" button, a confirmation message appears.
# frozen_string_literal: true
module AuditEvents
class RegisterRunnerAuditEventService < RunnerRegistrationAuditEventService
class RegisterRunnerAuditEventService < RunnerAuditEventService
def token_field
:runner_registration_token
end
......
# frozen_string_literal: true
module AuditEvents
class RunnerRegistrationAuditEventService < ::AuditEventService
# Logs an audit event related to a runner registration event
class RunnerAuditEventService < ::AuditEventService
# Logs an audit event related to a runner event
#
# @param [Ci::Runner] runner
# @param [String, User] author the entity initiating the operation (e.g. a runner registration or authentication token)
......@@ -43,10 +43,6 @@ module AuditEvents
raise NotImplementedError, "Please implement #{self.class}##{__method__}"
end
def author_class
raise NotImplementedError, "Please implement #{self.class}##{__method__}"
end
def runner_type
@runner.runner_type.chomp('_type')
end
......
# frozen_string_literal: true
module AuditEvents
class UnregisterRunnerAuditEventService < RunnerRegistrationAuditEventService
class UnregisterRunnerAuditEventService < RunnerAuditEventService
def token_field
:runner_authentication_token
end
......
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