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

Add default value for go-mod-path #30

Merged
merged 2 commits into from Aug 19, 2022
Merged

Conversation

jhutchings1
Copy link
Contributor

I noticed that we don't have a default value for the go-mod-path, even though it's usually at the root of the repository. I propose adding the default value here.

@jhutchings1 jhutchings1 requested a review from a team as a code owner August 18, 2022 23:56
@febuiles febuiles merged commit 499f61e into actions:main Aug 19, 2022
@jhutchings1 jhutchings1 deleted the patch-1 branch August 22, 2022 21:11
@jhutchings1
Copy link
Contributor Author

@febuiles Do we have automation pushing a release or do we need to cut that manually?

@febuiles
Copy link
Contributor

@jhutchings1 didn't get any feedback about this when inquiring earlier, I'll PR some instructions in the contribution doc this week, fix the tags and push a new version. If you want to do it by yourself these instructions should "just work" ™️: https://github.com/actions/dependency-review-action/blob/main/CONTRIBUTING.md#cutting-a-new-release

@febuiles
Copy link
Contributor

I've manually pushed a new release. With the latest action added the v1 tag has been automatically sync'd.

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.

None yet

3 participants