Add daily semconv check

[trask]

Runs build-dev.yml once a day and opens an issue in the semantic convention repository on failure.

cc @open-telemetry/specs-semconv-approvers

[meswapnilk]

@trask you may want to check the prettier check locally and update the PR?

[svrnm]

Thanks @trask!

@chalin please take a look, you know that build dev workflow best

[chalin]

Very cool.

I get the feeling that this workflow would be best kept in the semconv repo. WDYT?

[trask]

I get the feeling that this workflow would be best kept in the semconv repo. WDYT?

I'm not sure how to run the docs workflow from the semconv repo (maybe could submodule it in?)

[chalin]

I'm not sure how to run the docs workflow from the semconv repo (maybe could submodule it in?)

@svrnm once mentioned that it is possible to reference/call workflows from other repos. Is that right?

[trask]

@svrnm once mentioned that it is possible to reference/call workflows from other repos. Is that right?

yeah, what I didn't consider though is that the (semconv) workflow could directly check out the docs repo (no need to submodule), I'll try this out, thanks!

[trask]

yeah, what I didn't consider though is that the (semconv) workflow could directly check out the docs repo (no need to submodule), I'll try this out, thanks!

I think the problem is this:

If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses actions/checkout, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow.

I do think we could copy build-dev.yml from this repo into the semconv repo, and update the actions/checkout steps to check out the opentelemetry.io repo instead of the semconv repo.

I guess I see this as an integration test for the website repo, and so it doesn't seem that out-of-place to live in the website repo.

Maybe a better option instead of opening the issue in semconv repo is to open the issue in the website repo but tag the semconv maintainers on it?

[chalin]

Ok, given all that, I'd be opening to having the workflow run in this repo. I'd rather have the issue created in open-telemetry/semantic-conventions (at least for now).

[chalin]

/fix:format

[opentelemetrybot]

You triggered fix:format action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/12879013379

[opentelemetrybot]

fix:format failed or was cancelled. For details, see https://github.com/open-telemetry/opentelemetry.io/actions/runs/12879013379.

[chalin]

fix:format failed or was cancelled. For details, see https://github.com/open-telemetry/opentelemetry.io/actions/runs/12879013379.

Our bot doesn't have the permission to push updates to your workflow files:

To https://github.com/trask/opentelemetry.io.git
 ! [remote rejected]   HEAD -> daily-semconv-check (refusing to allow a GitHub App to create or update workflow `.github/workflows/build-semconv-daily.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/trask/opentelemetry.io.git'

@trask, you should update from main, and run npm run fix:format locally before repushing.

[trask]

/fix:format

[opentelemetrybot]

You triggered fix:format action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/12879782312

[opentelemetrybot]

fix:format failed or was cancelled. For details, see https://github.com/open-telemetry/opentelemetry.io/actions/runs/12879782312.

[trask]

@trask, you should update from main, and run npm run fix:format locally before repushing.

npm run fix:format fails locally for me (maybe because Windows?)

npm error code EINVALIDTAGNAME
npm error Invalid tag name "prettier${PRETTIER_AT_VERS}" of package "prettier$
{PRETTIER_AT_VERS}": Tags may not have any characters that encodeURIComponent encodes.

[trask]

Replaced by #5996

[trask]

new plan, I'm going to move the yml file out of workflows, then /fix:format then move it back 😅

[trask]

/fix:format

[opentelemetrybot]

You triggered fix:format action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/12879883331

[opentelemetrybot]

fix:format failed or was cancelled. For details, see https://github.com/open-telemetry/opentelemetry.io/actions/runs/12879883331.

[trask]

/fix:format

[opentelemetrybot]

You triggered fix:format action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/12879900677

[opentelemetrybot]

fix:format was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[chalin]

Let's give this a try. I'm thinking that we might want to trigger on commits to semconv main instead of a daily cron job, but we can tweak that later if needed.

[chalin]

new plan, I'm going to move the yml file out of workflows, then /fix:format then move it back 😅

😅 ... a lot of work, but it did the trick! 🙌🏻

Next time maybe consider locally (and temporarily) replacing npx prettier${PRETTIER_AT_VERS} by npx prettier@latest.

npm run fix:format fails locally for me (maybe because Windows?)

Right, we don't officially support builds from Windows. I've wanted to work on this in the past but I don't have a Windows environment to test from 🤷🏼‍♂️.

[trask]

Next time maybe consider locally (and temporarily) replacing npx prettier${PRETTIER_AT_VERS} by npx prettier@latest.

this worked! thanks