Skip to content

Feature/ci status watch#2091

Open
shodiBoy1 wants to merge 6 commits into
devonfw:mainfrom
shodiBoy1:feature/ci-status-watch
Open

Feature/ci status watch#2091
shodiBoy1 wants to merge 6 commits into
devonfw:mainfrom
shodiBoy1:feature/ci-status-watch

Conversation

@shodiBoy1

@shodiBoy1 shodiBoy1 commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

This PR adds ci status watch and external discussion observer workflows

Implemented changes:

  • New ci-status-watch.yml weekday-morning workflow that lists the workflows currently red on main and posts them as a single Teams card, so a broken CI is noticed in the Daily. Reports current state (a workflow stays listed until it's green again); creates no issues. Read-only (actions: read).
  • Extended issue-pr-observer.yml the daily digest now also reports new external GitHub Discussions (fetched via GraphQL, since they have no REST search). Issues/PRs and discussions are shown as two separate sections in the same card. Each source falls back to empty on error, so a failure in one still posts the other.

Testing instructions

  1. Make sure the repo secret TEAMS_WEBHOOK_URL is set (Teams incoming webhook).
  2. CI status watch: Actions -> "CI status watch" → Run workflow. If any workflow on main is red, a card with the list appears in Teams; otherwise the run log says all green and nothing is posted.
  3. Issue/PR/Discussion observer: Actions -> "External Issue, PR & Discussion Observer" -> Run workflow. New external issues/PRs/discussions from the look-back window appear as two sections; if there's nothing new, no message is sent.
  4. Check the run logs each step prints how many items it found.

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

  • When running mvn clean test locally all tests pass and build is successful
  • PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat). If no issue ID exists, title only.
  • PR top-level comment summarizes what has been done and contains link to addressed issue(s)
  • PR and issue(s) have suitable labels
  • Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
  • You followed all coding conventions
  • You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labeled
    with internal
  • You have formulated clear instructions on how to test your contribution under "Testing instructions"

@github-project-automation github-project-automation Bot moved this to 🆕 New in IDEasy board Jun 29, 2026
@shodiBoy1 shodiBoy1 self-assigned this Jun 29, 2026
@shodiBoy1 shodiBoy1 added SCM software-configuration-management (github actions, internal processes, git or github utilization) internal Nothing to be added to CHANGELOG, only internal story workflow GitHub actions (CI,CD,update urls/CVEs) labels Jun 29, 2026
@coveralls

coveralls commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 28427239286

Coverage increased (+0.03%) to 71.372%

Details

  • Coverage increased (+0.03%) from the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 16275
Covered Lines: 12112
Line Coverage: 74.42%
Relevant Branches: 7286
Covered Branches: 4704
Branch Coverage: 64.56%
Branches in Coverage %: Yes
Coverage Strength: 3.15 hits per line

💛 - Coveralls

@shodiBoy1 shodiBoy1 marked this pull request as ready for review June 29, 2026 21:27
@shodiBoy1 shodiBoy1 moved this from 🆕 New to Team Review in IDEasy board Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Nothing to be added to CHANGELOG, only internal story SCM software-configuration-management (github actions, internal processes, git or github utilization) workflow GitHub actions (CI,CD,update urls/CVEs)

Projects

Status: Team Review

Development

Successfully merging this pull request may close these issues.

2 participants