extension.json · main · repos / Growth / Community Configuration Example

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

How to register an account on GitLab. Due to spam, new accounts are locked until approved by an admin or the approver bot. Your GitLab account gets automatically approved within one hour if you are a member of Trusted Contributors in Gerrit, or a member of the Trusted-Contributors group in Phabricator and linked your Developer account to your Phabricator account. If none of these apply, you can file an unlock request to expedite access.

Support: mw:GitLab, how to host a project on GitLab, #wikimedia-gitlab on libera.chat, #GitLab on Phabricator.

Blame History

Reflect renaming of CommunityConfiguration services · bacead37

Michael Große authored Jun 04, 2024

In I74d14effc5dd60a8516769e6e9ca2349ebebc59d, we rename
WikiPageConfigReader to MediaWikiConfigReader. Reflect that renaming in
CommunityConfigurationExample as well.

Bug: T362863
Depends-On: I74d14effc5dd60a8516769e6e9ca2349ebebc59d
Change-Id: I27fecec7939d43900afd062f19c17c883d4f1941

bacead37

Admin message

Admin message

Admin message