Skip to content

Conversation

@alocay
Copy link
Contributor

@alocay alocay commented Aug 25, 2025

No description provided.

@alocay alocay requested a review from a team as a code owner August 25, 2025 19:45
@apollo-librarian
Copy link

apollo-librarian bot commented Aug 25, 2025

✅ Docs preview ready

The preview is ready to be viewed. View the preview

File Changes

0 new, 1 changed, 0 removed
* (developer-tools)/apollo-mcp-server/(latest)/install.mdx

Build ID: 547f136915a8b4c1c84de9c0
Build Logs: View logs

URL: https://www.apollographql.com/docs/deploy-preview/547f136915a8b4c1c84de9c0

- name: Configure git author
run: |
git config --local user.name "github-actions[bot]"
git config --local user.email "41898282+github-actions[bot]@users.noreply.github.com"
Copy link
Contributor

Choose a reason for hiding this comment

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

minor question, where does this email come from and can we assume it will be static?

I would have thought this would be part of a context object we can inject in, but that is unclear from the docs
https://docs.github.com/en/actions/reference/workflows-and-actions/contexts#github-context

Copy link
Contributor Author

Choose a reason for hiding this comment

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

From what I've gathered this is the default user and no-reply email for the github bot. Using this will show that the git commands run later are done by the github bot. This isn't ideal so I'm working with some folks to see if there's an Apollo automation account we can use instead.

@alocay alocay requested a review from swcollard August 26, 2025 14:01
@alocay alocay merged commit 3395691 into main Aug 26, 2025
7 checks passed
@alocay alocay deleted the gt-367-configure-github-bot-author branch August 26, 2025 14:36
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.

3 participants