Skip to content

Conversation

ymmt2005
Copy link

@ymmt2005 ymmt2005 commented Sep 18, 2025

The current procedure for configuring git does not allow it to push commits
besides the current repository, even if the app token may have access to other
repositories. It also does not allow git to clone such a repository.

This new procedure configures gh first and then calls gh auth setup-git
to configure git so it will work for any repository that the token has access to.

@ymmt2005 ymmt2005 requested a review from a team as a code owner September 18, 2025 07:35
@Copilot Copilot AI review requested due to automatic review settings September 18, 2025 07:35
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the git configuration procedure to properly enable pushing commits by configuring gh first and using gh auth setup-git instead of manually setting git user credentials. The changes address the issue where the previous procedure configured git but didn't allow actual push operations.

  • Simplifies the configuration process by leveraging gh auth setup-git instead of manual git config commands
  • Moves the tip about finding bot user IDs to appear before the configuration section for better readability
  • Updates the procedure title to reflect that it now configures both gh and git CLI tools

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@ymmt2005
Copy link
Author

ymmt2005 commented Sep 18, 2025

It seems #273 and #285 try to solve the same issue with a different approach.
Though I'm unsure which one will be the best, I hope at least one of them will be merged.

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 this pull request may close these issues.

1 participant