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

move various tools to avoid main func collisions #947

Merged
merged 1 commit into from
Aug 16, 2024
Merged

Conversation

jmhodges
Copy link
Contributor

@jmhodges jmhodges commented Aug 15, 2024

These Go files all contained func mains that conflicted with other
mains in the same directory. Only one of these tools are used in our
build or referenced in our docs, and that use (in our softhsm
Dockerfile) is adjusted.

This was done because various tools complain and break. For instance,
go build ./.... Now the ... alias in Go tooling works again.

This was figured out while working on porting the linting work to GitHub
Actions.

Updates AUT-192
Updates AUT-197

@jmhodges jmhodges marked this pull request as ready for review August 15, 2024 14:27
@jmhodges jmhodges requested review from a team as code owners August 15, 2024 14:27
@jmhodges jmhodges requested review from oskirby and removed request for a team August 15, 2024 14:27
These Go files all contained `func main`s that conflicted with other
`main`s in the same directory. Only one of these tools are used in our
build or referenced in our docs, and that use (in our softhsm
Dockerfile) is adjusted.

This was done because various tools complain and break. For instance,
`go build ./...`. Now the `...` alias in Go tooling works again.

This was figured out while working on porting the linting work to GitHub
Actions.

Updates AUT-192
Updates AUT-197
jmhodges added a commit that referenced this pull request Aug 15, 2024
Now that we've stopped our tools from conflicting over `func main`, we
can use the Go tooling's `./...` alias to make them operate over all of
our packages. See `go help packages` for more on `...`. (Those conflicts
were solved in #947).

This means we no longer have to remember to update this variable
everytime we want to test or lint a new package in CI and locally.
jmhodges added a commit that referenced this pull request Aug 15, 2024
Now that we've stopped our tools from conflicting over `func main`, we
can use the Go tooling's `./...` alias to make them operate over all of
our packages. See `go help packages` for more on `...`. (Those conflicts
were solved in #947).

This means we no longer have to remember to update this variable every
time we want to test or lint a new package in CI and locally.
@jmhodges jmhodges requested a review from bhearsum August 16, 2024 11:07
@jmhodges jmhodges merged commit c95ca79 into main Aug 16, 2024
15 checks passed
jmhodges added a commit that referenced this pull request Aug 26, 2024
Now that we've stopped our tools from conflicting over `func main`, we
can use the Go tooling's `./...` alias to make them operate over all of
our packages. See `go help packages` for more on `...`. (Those conflicts
were solved in #947).

This means we no longer have to remember to update this variable every
time we want to test or lint a new package in CI and locally.
jmhodges added a commit that referenced this pull request Aug 26, 2024
Now that we've stopped our tools from conflicting over `func main`, we
can use the Go tooling's `./...` alias to make them operate over all of
our packages. See `go help packages` for more on `...`. (Those conflicts
were solved in #947).

This means we no longer have to remember to update this variable every
time we want to test or lint a new package in CI and locally.
jmhodges added a commit that referenced this pull request Aug 26, 2024
Now that we've stopped our tools from conflicting over `func main`, we
can use the Go tooling's `./...` alias to make them operate over all of
our packages. See `go help packages` for more on `...`. (Those conflicts
were solved in #947).

This means we no longer have to remember to update this variable every
time we want to test or lint a new package in CI and locally.

Updates AUT-192
jmhodges added a commit that referenced this pull request Aug 26, 2024
Now that we've stopped our tools from conflicting over `func main`, we
can use the Go tooling's `./...` alias to make them operate over all of
our packages. See `go help packages` for more on `...`. (Those conflicts
were solved in #947).

This means we no longer have to remember to update this variable every
time we want to test or lint a new package in CI and locally.

Updates AUT-192
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.

2 participants