Added the DOC pop in web to explain the PAT handling. #347
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello @cyclotruc I didn't understand what your commit say ,do i have to merge any thing in my forked branch ? |
|
Thank you for your efforts @RautAtharv07! We felt this to be too verbose and went for a more subtle approach #348. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a help popup/modal to explain how Personal Access Tokens (PATs) are handled, addressing issue #321.
🔧 What’s Included:
A modal with clear details on PAT usage, privacy, and frontend behavior
"Got it" button styled to match the existing Ingest button for consistent UI/UX
Fully responsive layout matching the project’s design language
📋 Content Shown in Modal:
PAT is never stored on servers or databases
It is used only once for cloning and then discarded
No frontend/local storage caching
