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

Work in Progress: initial configuration for github actions migration. #292

Closed
wants to merge 87 commits into from

Conversation

kaladay
Copy link
Contributor

@kaladay kaladay commented Jan 8, 2021

this is a test.

jcreel and others added 30 commits November 20, 2020 15:07
Github reports: "a step cannot have both the `uses` and `run` keys".
@kaladay kaladay closed this Jan 12, 2021
@kaladay kaladay reopened this Jan 13, 2021
@coveralls
Copy link

coveralls commented Jan 13, 2021

Coverage Status

Coverage decreased (-0.03%) to 47.477% when pulling 912b109 on sprint-action-290-sage into 7b0aead on sprint-action-staging.

The idea here is that by appending "-test", it can be determined what the default behavior for restore-keys is when undefined.
This will helps us avoid assuming the behavior.

If the default behavior does find the nearest match, then the nearest match should be the existing hash (without the "-test").
pom.xml Outdated Show resolved Hide resolved
@kaladay kaladay closed this Jan 19, 2021
@ghost ghost deleted the sprint-action-290-sage branch February 3, 2021 14:10
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.

4 participants