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

clean.yml could have become unnecessary #35

Closed
ldeluigi opened this issue Nov 15, 2020 · 3 comments
Closed

clean.yml could have become unnecessary #35

ldeluigi opened this issue Nov 15, 2020 · 3 comments

Comments

@ldeluigi
Copy link
Contributor

I found this setting under Actions:

image

@djspiewak
Copy link
Collaborator

Hmm, can it be set to 0? Part of the problem here is the fact that build artifacts in this workflow are used to pass data between jobs, so they're entirely ephemeral and should never be retained.

@ldeluigi
Copy link
Contributor Author

ldeluigi commented Nov 15, 2020

image

Sadly, no.

Meanwhile, Travis CI has changed their policy and now basically forces you to pay money so I'm expecting a progressive migration of many big projects to GitHub Actions: I hope this new influx of users will make GitHub pay more attention to current issues and needs.

@djspiewak
Copy link
Collaborator

Meanwhile, Travis CI has changed their policy and now basically forces you to pay money so I'm expecting a progressive migration of many big projects to GitHub Actions: I hope this new influx of users will make GitHub pay more attention to current issues and needs.

Yeah I'm experiencing exactly this as well. I had already migrated to gha, but TravisCI has definitely been a serious forcing function in a lot of other ecosystems, such as Typelevel.

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

No branches or pull requests

2 participants