-
Notifications
You must be signed in to change notification settings - Fork 182
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
[chore] Enbled make fix can fix table format #1699
base: main
Are you sure you want to change the base?
Conversation
docs/attributes-registry/android.md
Outdated
@@ -13,16 +13,16 @@ | |||
|
|||
The Android platform on which the Android application is running. | |||
|
|||
| Attribute | Type | Description | Examples | Stability | | |||
|---|---|---|---|---| | |||
| Attribute | Type | Description | Examples | Stability | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these files are auto-generated, we should not modify them (and I think whitespaces in jinja are too complicated to format them in this way)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lmolkova make fix-format
will update the tables
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe we don't use format checks in the workflows/CI and can probably remove this check from the makefile.
Wonder what @open-telemetry/specs-semconv-maintainers think
Yes, we can discuss if we need |
as you can see it breaks other checks (registry validation). Personally, I don't see a benefit in format check in MD + yaml repo with MD and yaml lint checks. |
Thanks @lmolkova , with that, shall we remove both |
I don't use |
fwiw, the only thing I ever use is |
Signed-off-by: Guangya Liu <[email protected]>
Fixes #1692
Changes
Please provide a brief description of the changes here.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]