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

Use githubgen tool from go-build-tools #37412

Merged
merged 24 commits into from
Jan 23, 2025

Conversation

mowies
Copy link
Member

@mowies mowies commented Jan 22, 2025

Description

  • This PR
    • switches over all usages of the githubgen tool to the new tool location by adjusting make targets and the check-code-owners pipeline
    • introduces the new githubgen tool at its latest v0.17.0 version
    • adds make gengithub to the commands to run in the contribution guide
    • re-generates the codeowners and allowlist files using the new githubgen tool (only cosmetic changes)

Link to tracking issue

Part of #37294

Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
@atoulme
Copy link
Contributor

atoulme commented Jan 22, 2025

Before we delete the code under cmd/githubgen, it would be good form to deprecate it formally and have a release with it. This follows golang best practices. I would keep the PR focused on swapping between githubgen locations.

@mowies
Copy link
Member Author

mowies commented Jan 23, 2025

@atoulme sounds good. Then I will reinstate the githubgen files in this PR and open a separate one to actually remove them at a later stage.

@mowies mowies marked this pull request as ready for review January 23, 2025 09:04
@mowies mowies requested a review from a team as a code owner January 23, 2025 09:04
@mowies
Copy link
Member Author

mowies commented Jan 23, 2025

@atoulme PR should be ready for review now :)

@mowies
Copy link
Member Author

mowies commented Jan 23, 2025

the failing check-codeowners workflow is to be expected since the codeowners and allowlist files were changed in this PR and the tool to generate and check them also changed

Copy link
Contributor

@atoulme atoulme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@songy23 songy23 merged commit b731208 into open-telemetry:main Jan 23, 2025
166 of 167 checks passed
@github-actions github-actions bot added this to the next release milestone Jan 23, 2025
chengchuanpeng pushed a commit to chengchuanpeng/opentelemetry-collector-contrib that referenced this pull request Jan 26, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
- This PR
- switches over all usages of the githubgen tool to the new tool
location by adjusting make targets and the check-code-owners pipeline
  - introduces the new githubgen tool at its latest v0.17.0 version 
- adds `make gengithub` to the commands to run in the contribution guide
- re-generates the codeowners and allowlist files using the new
githubgen tool (only cosmetic changes)

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Part of
open-telemetry#37294


<!--Please delete paragraphs that you did not use before submitting.-->

---------

Signed-off-by: Moritz Wiesinger <[email protected]>
@mowies mowies deleted the move-githubgen branch January 27, 2025 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants