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

post-release: fetch the full repo, not a shallow clone #1189

Merged
merged 1 commit into from
May 13, 2022

Conversation

jordigh
Copy link
Contributor

@jordigh jordigh commented May 12, 2022

Links

Closes #1188

Details

By default, github's actions/checkout action will do a shallow clone
of a single commit, without history. Since our workflow requires a
merge, we need the full history in order to be able to perform the
merge.

By default, github's actions/checkout action will do a shallow clone
of a single commit, without history. Since our workflow requires a
merge, we need the full history in order to be able to perform the
merge.
@jordigh
Copy link
Contributor Author

jordigh commented May 13, 2022

I just ran the workflow from this branch and it succeeded this time:

https://github.com/newrelic/node-newrelic/runs/6425238283?check_suite_focus=true

@bizob2828 bizob2828 merged commit 6fe5395 into main May 13, 2022
@github-actions github-actions bot mentioned this pull request May 13, 2022
@coreyarnold coreyarnold deleted the fix-post-release-gh-action branch May 18, 2023 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Github action update-rpm-and-docs fails with git merge problem
2 participants