Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update Personal Access Token Documentation Link in README #1904

Closed
vamsi4845 opened this issue May 19, 2024 · 1 comment
Closed

chore: Update Personal Access Token Documentation Link in README #1904

vamsi4845 opened this issue May 19, 2024 · 1 comment

Comments

@vamsi4845
Copy link

vamsi4845 commented May 19, 2024

The current documentation for creating a GitHub Personal Access Token in the README points to an outdated version (GitHub Enterprise Server 3.4) of the guide. The latest version of the guide is available for GitHub Enterprise Server 3.13.

Steps to Reproduce:

Navigate to the README in the repository.
Find the section Troubleshooting mentioning the creation of a GitHub Personal Access Token.
Observe the link pointing to (https://docs.github.com/en/enterprise-server@3.4/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).

Proposed Solution:
Update the link to point to the latest documentation for creating a GitHub Personal Access Token, which is available at (https://docs.github.com/en/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).

@vamsi4845 vamsi4845 changed the title Chore: Update Personal Access Token Documentation Link in README chore: Update Personal Access Token Documentation Link in README May 19, 2024
@xgreenx
Copy link
Collaborator

xgreenx commented May 27, 2024

Thank you for your contribution, but the old link still works. Closing this issue for now.

@xgreenx xgreenx closed this as completed May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants