Conversation
Cancel the exact in-flight provider runner, fail loudly when first-run repair collides with an active generation, and re-validate HTTP, git, shell, approval, and GitHub update paths at the execution boundary.
Drop the AI tells, keep the facts, and say what Bar Tender actually does.
fix: close generation races and tighten execution boundaries
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
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 pull request updates Bar Tender's documentation and issue templates for clarity, conciseness, and improved user guidance. The changes modernize language, clarify instructions, and improve the consistency of terminology across the project. No code or functionality is altered—these are documentation and template improvements only.
Documentation improvements:
README.md,CONTRIBUTING.md,PRIVACY.md,CHANGELOG.md,CITATION.cff: Rewrote and clarified descriptions, setup instructions, privacy statements, and changelog entries for better readability and accuracy. Language is now more direct, user-focused, and consistent with current project terminology. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Issue template refinements:
.github/ISSUE_TEMPLATE/feature_request.yml,.github/ISSUE_TEMPLATE/bug_report.yml: Updated template descriptions and field labels to be more action-oriented and helpful for users reporting issues or requesting features. [1] [2]These updates make the project's documentation and templates more approachable and easier to understand for both users and contributors.