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
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, yaml
- Domain
- devops
Research direction
Read .github/workflows/recompile_agentic_workflows.yml and compare it with the linked commit diff. Add the equivalent OpenTelemetry instrumentation step after workflow compilation, using the specified action and secret-backed environment values. Done when the workflow contains the equivalent step and its YAML structure matches the surrounding workflow.
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
- C++
- Stars
- 2
- Forks
- 0
- Avg merge
- 13m
- Merged PRs (30d)
- 20
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/DXGIOutputDuplication
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
plengauer/DXGIOutputDuplication#10 ·
Maintainers usually reply within 1 day
All issues in plengauer/DXGIOutputDuplication
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
foxglove/mcap#1907 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Documentation
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
qbittorrent/qBittorrent#25127 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
telegramdesktop/tdesktop#31505 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day