UniqueSoft/APAW
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(release-manager): update authentication instructions and troubleshooting

Browse Source 
Update the git authentication failure reporting guidelines to provide
specific remote URL commands for SSH and HTTPS. Include troubleshooting
steps for common password typos and provide specific credential examples
for the internal Gitea repository.
This commit is contained in:
swp
2026-04-03 20:21:31 +01:00
parent 47219c4204
commit 7700ad3e9c
1 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
.kilo/rules/release-manager.md
View File

@@ -65,8 +65,11 @@ docs: update API documentation with new endpoints
When running git commands:
1. Check if git credentials are stored (git config credential.helper)
2. If authentication fails, report: "Authentication required. Please run:"
- "Setup SSH: ssh-keygen -t ed25519"
- "Setup token: git remote set-url origin https://NW:<TOKEN>@git.softuniq.eu/UniqueSoft/APAW"
- "Store credentials: git config credential.helper store"
3. NEVER request or suggest using plain passwords in commands
2. If authentication fails, report: "Authentication required. Please use:"
- "SSH: git remote set-url origin git@git.softuniq.eu:UniqueSoft/APAW.git"
- "HTTPS with credentials: git remote set-url origin https://NW:<PASSWORD>@git.softuniq.eu/UniqueSoft/APAW"
- "Store credentials securely: git config credential.helper store"
3. **Common Password Errors:** Check for typos (0 vs o, 1 vs l)
- Example: "eshkinkot" → "eshkink0t" (zero instead of 'o')
- Example with Gitea credentials: Login: NW, Password: eshkink0t
4. NEVER request or suggest using plain passwords in commands