Template update requires manual application (a977eeb7d3e7fc481e7e59521ffea7492a6ea14a)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 77/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, shell
- Domain
- ci-cd, observability
Research direction
Open .github/workflows/recompile_agentic_workflows.yml and review the existing compile and push steps. Add the OpenTelemetry instrumentation action after workflow compilation, using the endpoint and headers secrets shown in the issue. Confirm the workflow still parses and that instrumentation runs before the generated changes are pushed.
Written by the indexing model from the issue text.
Description
Template workflows have been updated but the diff could not be automatically applied to this repository. Apply a change that is semantically equivalent to the patch here.
Commit
Re-deploy OpenTelemetry instrumentation after recompiling agentic workflows (recompile_aw template) (#560)
See: https://github.com/plengauer/plengauer.github.io/commit/a977eeb7d3e7fc481e7e59521ffea7492a6ea14a
Diff
diff --git a/.github/workflows/recompile_agentic_workflows.yml b/.github/workflows/recompile_agentic_workflows.yml
index c0d3b8c..667efe5 100644
--- a/.github/workflows/recompile_agentic_workflows.yml
+++ b/.github/workflows/recompile_agentic_workflows.yml
@@ -24,6 +24,12 @@ jobs:
- run: |
gh extension install github/gh-aw
gh aw compile --approve
+ - uses: plengauer/opentelemetry-github/actions/instrument/deploy-local@a3202770e6f9c17a81f2a7fd1073352b814d99b1 # v5.63.1
+ with:
+ github_token: ${{ env.GH_TOKEN }}
+ env:
+ OTEL_EXPORTER_OTLP_ENDPOINT: '${{ secrets.OTEL_EXPORTER_OTLP_ENDPOINT }}'
+ OTEL_EXPORTER_OTLP_HEADERS: '${{ secrets.OTEL_EXPORTER_OTLP_HEADERS }}'
- id: push
run: |
if [ -z "$(git status --porcelain)" ]; then exit 0; fi
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- Avg merge
- 49m
- Merged PRs (30d)
- 37
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from plengauer/Utilities
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 35/100
plengauer/Utilities#491 · 1 comment ·
Maintainers usually reply within 1 day
-
[aw] Detection RunsOpenagentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 1/100
plengauer/Utilities#490 · 4 comments ·
Maintainers usually reply within 1 day
All issues in plengauer/Utilities
Similar issues
-
Add dependabotOpenfeat
Difficulty 2/5 Under an hour Newbie friendliness 72/100
open-nudge/opentemplate#204 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
wso2/product-integrator-mi#5099 ·
Maintainers usually reply within 1 day
-
Standalone Unix updater reports success when curl fails (`curl | sh` masks the exit status); Windows path is unaffectedPossibly taken @akhil9tiet claimed this today. Openbug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openai/codex#54465 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ChrisTitusTech/dwm-titus#397 ·
Maintainers usually reply within 1 day