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

Workflows fail on initial commit #20

Open
shifqu opened this issue May 11, 2021 · 3 comments
Open

Workflows fail on initial commit #20

shifqu opened this issue May 11, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@shifqu
Copy link
Owner

shifqu commented May 11, 2021

Clearly the knowledge on github actions should be improved.

Linting is trimmed down, but testing is still done on multiple os'es and multiple python versions. This should be trimmed down as well

@shifqu
Copy link
Owner Author

shifqu commented May 12, 2021

With this repo being private, and us doing a cruft check in lint.sh, we would need to add secrets to each repo created... which is a hassle and conflicts with cookiecutter's ease of use

@shifqu shifqu added the bug Something isn't working label May 12, 2021
@shifqu
Copy link
Owner Author

shifqu commented May 17, 2021

Some work has been done on this over the weekend, but the pipelines are still failing.
For some reason gh actions cannot pull this repo in the cruft check command. I assume it will be some kind of caching, because this repo used to be private.

@shifqu
Copy link
Owner Author

shifqu commented Jun 28, 2021

After some more research, I found out that I was using git protocol, which does not work by default in gh actions. So updating to use https protocol solved that one.

Retest this issue, as I think it is solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant