Suzanne Selhorn (8230ea78) at 17 Mar 01:54
Generating pot file
Suzanne Selhorn (8a6c65c2) at 17 Mar 01:23
Fixed code issue
(A few pipeline issues still, but hopefully it's almost ready
Suzanne Selhorn (8b420ba0) at 17 Mar 00:35
A few more fixes
From the related issue, here is a summary of the changes so you can see it more easily:
| Before | After |
|---|---|
| a sign up | a new user account |
| sign-up restrictions | new user account restrictions |
| sign-up enabled | allow new user accounts |
| new sign-ups | new user accounts |
| after sign-up text | text shown to new users |
| allowed domains for new sign-ups | domains allowed for new users |
| denied domains for sign-ups | domains denied to new users |
Hi @lciutacu @kpaizee
doc/administration/settings/sign_up_restrictions.md (I used a mix of "prevent new accounts" and "disable new user account creation" -- maybe this will help people who are searching? Or maybe we should pick one string and be consistent. You'll see when you review the page.)sign-up, sign up and the plural forms. It's a first iteration and it doesn't include register so I'll have to do follow-ups, but this MR does the bulk of the initial updates (it was a lot!)Side note: I had a failing pipeline that said, rspec-predictive-artifact-collector: one job can only need 50 others, but you have listed 55. See needs keyword documentation for more details and in slack, someone mentioned the fix is a tier 3 pipeline, so that's what I've done here.
cc: @efergen
Suzanne Selhorn (c836bc9f) at 16 Mar 21:29
Fixing pipeline error
Suzanne Selhorn (fdb71844) at 16 Mar 19:32
More link fixes
Suzanne Selhorn (75ec026b) at 16 Mar 19:03
Fixing ruby file
Suzanne Selhorn (2c14ac6b) at 16 Mar 18:50
A few link fixes
Suzanne Selhorn (58917d2e) at 16 Mar 18:21
Adding more files
Suzanne Selhorn (3df14862) at 16 Mar 16:14
Suzanne Selhorn (25f598e1) at 16 Mar 16:14
Merge branch 'fneill-update-nav-for-dap' into 'main'
... and 1 more commit
Moves Triggers under Flows. This helps make the association between triggers and flows more clear for users.
Moves Code Suggestions further down the nav. This is so that Sessions and Customization are grouped next to Agents and Flows.
Link to the merge request that introduced the new page: NA
Give the MR a descriptive title.
Optional. Link to the review app showing the new page:
Thanks @fneill Good updates!
Moves Triggers under Flows. This helps make the association between triggers and flows more clear for users.
Moves Code Suggestions further down the nav. This is so that Sessions and Customization are grouped next to Agents and Flows.
Link to the merge request that introduced the new page: NA
Give the MR a descriptive title.
Optional. Link to the review app showing the new page:
@fneill Have you seen this? https://storage.googleapis.com/dap-prompt/dap_prompt_library.html
Actually it looks like they put it here: https://about.gitlab.com/gitlab-duo/prompt-library/
Just playing with ideas. Will work on it more next week--
Works with this markdown:
---
title: You've been added to a project
layout: quickref
---
When you open a GitLab project, you land on the project overview. This page explains what you're seeing and where to go depending on what you need to do.
## The screen you're on
### The project overview
*The project overview β the default view when you open any GitLab project.*
1. **Left sidebar** β Navigate the project from here. Plan, Code, and Build sections are in the left sidebar.
1. **File list** β The project repository. Click any file to view it. Whether you can edit depends on your role.
1. **README.md** β Displayed automatically if the project has one. Read this first.
1. **`.gitlab-ci.yml`** β The pipeline configuration file. If this file exists, automated jobs run when code is pushed.
---
## Where to go next
### Navigate by what you need to do
- **View tasks and progress**
Go to **Plan** βΊ **Issues** or **Boards**.
- **View or comment on code changes**
Go to **Code** βΊ **Merge requests**.
- **Edit a file**
Open a file from the repository, then select **Edit**.
- **Check pipeline status**
Go to **Build** βΊ **Pipelines**.
---
## Start here
> Open **README.md** from the file list. Then go to **Plan** > **Issues** to see what work is currently tracked. Those two things give you the most context about a project before you do anything else.
[Next: Edit a file β](/get-started/first-project/edit-a-file/)These are strongly recommended to assist reviewers and reduce the time to merge your change.
Numbered steps to set up and validate the change are strongly suggested.
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
#tech-docs-localization slack channel.
The translation tooling might need to be updated, for example if new syntax is added or existing syntax rendering is changed.Suzanne Selhorn (1d04e001) at 13 Mar 22:51
Adding some styles