You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other (please describe): adding a specific piece of info to avoid confusion.
Current State
The public documents provide an easy guide with steps to add users. But in order to prevent confusion or errors during the process, the steps should emphasize the importance of entering the handle accurately.
Requested Changes
Add a sentence explaining that the GitHub/Bitbucket handle should be written exactly as it is (the system identifies upper-case, lower-case, hyphen, underscores), this could help users to be more careful while adding another members.
Suggested Content
In step number 1 ("1. Select one of the available tabs"), after the first sentence, we could add something like this:
Select one of the available tabs
Type the user's handle, e.g. TomFern, or select the user from the list. The system is case-sensitive and considers all characters, so please ensure the handle is entered exactly to avoid errors.
Additional Information
Affects Version
Cloud Semaphore
Community Edition (specify version):
The text was updated successfully, but these errors were encountered:
## 📝 Description
This PR adds v1.3 pages for CE.
In addition, it adds the following small changes:
- note on exporting audit logs in CSV format
(#353)
- note about inviting GitHub and BitBucket users
(#354)
- note about GitHub users being case-sensitive
(#355)
- note about GitHub PRs stuck due to renamed pipelines
(#360)
## ✅ Checklist
- [X] I have tested this change
- [ ] This change requires documentation update
Uh oh!
There was an error while loading. Please reload this page.
Documentation Location
https://docs.semaphoreci.com/using-semaphore/organizations#add-people
Type of Documentation Issue
Current State
The public documents provide an easy guide with steps to add users. But in order to prevent confusion or errors during the process, the steps should emphasize the importance of entering the handle accurately.
Requested Changes
Add a sentence explaining that the GitHub/Bitbucket handle should be written exactly as it is (the system identifies upper-case, lower-case, hyphen, underscores), this could help users to be more careful while adding another members.
Suggested Content
In step number 1 ("1. Select one of the available tabs"), after the first sentence, we could add something like this:
Additional Information
Affects Version
The text was updated successfully, but these errors were encountered: