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

Rejected Remote Issue #65

Closed
AlexMachin1997 opened this issue Jul 5, 2020 · 2 comments
Closed

Rejected Remote Issue #65

AlexMachin1997 opened this issue Jul 5, 2020 · 2 comments
Labels
question Further information is requested

Comments

@AlexMachin1997
Copy link

Hi,

I've been using lint-action for a while now and most of the time it's been fine, however, I've noticed after creating a new "feature" and my linitng task is failing. I get the following output:

image

Im not entirely sure what I can do to solve this issue, is there a way to get a new github token for the current branch or is this related to the token scoping Github has put in place ?

I really want to add this to our Github flow at work, I've used in all my personal projects and I love it, but I keep getting errors like this and I don't understand them fully or how to fix them.

Any help would greatly be appreciated 👍

Project Link: https://github.com/AlexMachin1997/TheOpenMovieDB-React-Example/actions

@ocean90
Copy link
Member

ocean90 commented Jul 30, 2020

Sounds like the same issue mentioned in #74. The linter seems to change the workflow file and committing the change isn't allowed for the default GitHub token. A fix would be to ensure that the file has the correct style by running the linter and committing the changes locally.

@ocean90 ocean90 added the question Further information is requested label Jul 30, 2020
@AlexMachin1997
Copy link
Author

Yeah that's my post aswell lol.

I basically spoke to some people on Githubs new forum system and yeah the eslint tries to modify the workflow files, it makes sense it does this as it's trying to fix an issue with the code. However, in this particular instance we don't need it to, there has got to be a away to have an internal eslintignore.

For now anyone else having this issue should just tell eslint to ignore .github directory.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants