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.

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

fix: change to deploy_key #254

Merged
merged 1 commit into from
Dec 4, 2024
Merged

fix: change to deploy_key #254

merged 1 commit into from
Dec 4, 2024

Conversation

Lash-L
Copy link
Collaborator

@Lash-L Lash-L commented Dec 4, 2024

No description provided.

@Lash-L Lash-L merged commit de0a0c7 into main Dec 4, 2024
7 checks passed
@Lash-L
Copy link
Collaborator Author

Lash-L commented Dec 5, 2024

@humbertogontijo

They key you have seems to still have
-----END OPENSSH PRIVATE
KEY-----

and -----BEGIN OPENSSH PRIVATE
KEY-----
in it

@Lash-L
Copy link
Collaborator Author

Lash-L commented Dec 5, 2024

@humbertogontijo What do you think about increasing my permissions so I can get this figured out. I think it would be a lot easier if I was able to create keys and test things.

You can change it back right after we get this fixed if you would like. This whole thing is just a bit aggravating and I would like it done. So I can actually continue making code improvements

Edit: although I guess if you bumped my permissions back down it would break again as if It were going off of my PAT then when my permissions went down it would fail.

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.

2 participants