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.

Sign up for GitHub

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

Jump to bottom

GitHub actions still rely on SSH key to push code #567

Closed
joeparsons opened this issue Sep 22, 2022 · 0 comments
Closed

GitHub actions still rely on SSH key to push code #567

joeparsons opened this issue Sep 22, 2022 · 0 comments
Assignees
@joeparsons
Labels
bug Something isn't working

Comments

@joeparsons
Copy link
Member

Problem/Motivation

Our Build & deploy review site and Create Release GH actions workflows still both rely on an old SSH key to push changes back to the repo.

Describe the bug

https://github.com/az-digital/arizona-bootstrap/blob/main/.github/workflows/review-site.yml#L69
https://github.com/az-digital/arizona-bootstrap/blob/main/.github/workflows/release.yml#L17

Proposed resolution

Replace these SSH keys with our organization bot user's token.
@joeparsons joeparsons added the bug Something isn't working label Sep 22, 2022
@joeparsons joeparsons self-assigned this Sep 22, 2022
@joeparsons joeparsons changed the title GitHub actions still rely on SSH key to push code. GitHub actions still rely on SSH key to push code Sep 22, 2022
joeparsons added a commit that referenced this issue Sep 22, 2022
@joeparsons
Closes #567: Use bot user token instead of old SSH key to push change…
30260cd 
…s back to repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joeparsons joeparsons

Labels
bug Something isn't working
Projects
No open projects
2.5.0 Release (9/23/22)
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joeparsons