Problem/Motivation
After reading the page on https://new.drupal.org/drupalorg/gitlab-custom-commands it is not clear for a new user on how those command should be executed. This leads to a problem where one end up "searching" for the command, which doesn't perform the expected outcome.
Steps to reproduce
Let say you want to execute `/do:access`
- Go to the following url https://git.drupalcode.org/project/drupalorg/-/merge_requests/498
- Start typing `/`
- The focus of the user automatically shifts to the search bar on top. there after typing "do:access" would perform search.
Proposed resolution
Update documentation to explain to the user, these commands are to be performed as "comment" on the issue.
Remaining tasks
- Agree on proposed text for update
- Update https://git.drupalcode.org/project/drupalorg/-/blob/1.0.x/src/Controller...
User interface changes
- N/A
API changes
- N/A
Data model changes
- N/A
Issue fork drupalorg-3591062
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #4
d34dman commentedProposal to add following text
Comment #5
fjgarlin commentedOnly on the issue (work item), NOT on the MR.
Comment #6
fjgarlin commentedI also don’t think we need to mention the other types where you don’t need to type since we are mentioning the place where they should, the comment.
Comment #7
d34dman commented- Removed the reference to "MR"
- Removed extra info surrounding search
So the text is now as follows,
<p>These commands must be posted as a <strong>comment</strong> on the issue (work item).</p>Comment #8
fjgarlin commentedI added one more sentence. Merged.
It will go with the next deployment, probably tomorrow.
Thanks.