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: specify x-access-token #249

Merged
merged 1 commit into from
Nov 20, 2024
Merged

fix: specify x-access-token #249

merged 1 commit into from
Nov 20, 2024

Conversation

Lash-L
Copy link
Collaborator

@Lash-L Lash-L commented Nov 20, 2024

No description provided.

@Lash-L Lash-L merged commit e9f319b into main Nov 20, 2024
7 checks passed
@Lash-L
Copy link
Collaborator Author

Lash-L commented Nov 20, 2024

@humbertogontijo Can you try a manual push using the GH_TOKEN? Still getting auth issues

@humbertogontijo
Copy link
Owner

I'm away from my pc. Can you create a simple PR? I guess if I merge it here it will be a commit from my user

@Lash-L
Copy link
Collaborator Author

Lash-L commented Nov 20, 2024

I was more interested in the specific token's auth - if you merge it I don't know if that will answer the question.

I'm going to get rid of semantic release I think. It has been too much of a pain. going to adopt another means of automatically doing it all.

@humbertogontijo
Copy link
Owner

I was able to change readme file from mobile. It's running

@humbertogontijo
Copy link
Owner

You now are a owner of the repository. I think you can do everything on a fork(even a release) before creating a PR. Maybe that will be an easier approach.
And you can create a PR after a successfully release. What you think?

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