feat: add first-interaction workflow for new contributors by HosurSharanamma · Pull Request #42 · eclipse-opensovd/cicd-workflows

HosurSharanamma · 2026-05-27T20:56:02Z

Summary

Adds a first-interaction.yml workflow that automatically posts a
welcome comment when someone opens their first issue or pull request
in the repository.

Motivation

Identified as a gap in issue #38 (CI parity analysis: opensovd-core
vs cicd-workflows). The opensovd-core repository already has this
workflow; this change brings cicd-workflows to parity.

Changes

Added .github/workflows/first-interaction.yml using
actions/first-interaction@v1
Posts a welcome message on first issues reminding contributors to
follow the contribution guidelines
Posts a welcome message on first PRs reminding contributors about
CI checks and the Eclipse DCO sign-off requirement

Testing

Ran uv run https://raw.githubusercontent.com/eclipse-opensovd/cicd-workflows/main/run_checks.py locally — all checks passed
Workflow syntax validated by check yaml and yamlfmt hooks

Relates to #38

alexmohr

Thank for your pull request :)

alexmohr

Awesome, thank you!

lh-sag · 2026-05-29T07:29:18Z

@@ -0,0 +1,45 @@
+# SPDX-License-Identifier: Apache-2.0
+# SPDX-FileCopyrightText: 2025 The Contributors to Eclipse OpenSOVD (see CONTRIBUTORS)


Please use 2026.

The trailing (see CONTRIBUTORS) is not common, I have not seen it in SCORE either. @alexmohr what was the intend of this remark and file. Could we simply remove it, at least he appearance in the comment.

Right now it is necessary to keep (see CONTRIBUTORS) otherwise the pipeline complains that the copyright header does not match. Year can be adjusted.
I'm not sure why we're using the copyright header with CONTRIBUTORS iirc @floroks was deeper involved in the discussion.

I'll clarify with the compliance people if this is necessary for some legal reasons, I'll report back

So feedback from our MBTI compliance people is pretty much what @lh-sag suggested :)

We can drop the (see Contributors) but keeping the block about notice etc (which no one discussed to remove here, just mentioning it for clarity) should be kept, because an Apache 2.0 licensed software must be shipped with a notice file if one is contained and mentioning it in the copyright makes it harder to miss the notice file (in theory at least).

Imho would make sense to do this in a follow up though.

#56 <-- follow up to fix this, as this is out of scope here.

lh-sag · 2026-05-29T07:31:49Z

+            - Make sure CI checks pass before requesting a review.
+            - Eclipse projects require a **DCO sign-off** on every commit:
+              use `git commit -s` or add `Signed-off-by: Your Name <email>` manually.
+            - See [CONTRIBUTING.md](https://github.com/eclipse-opensovd/opensovd/blob/main/CONTRIBUTING.md) for details.


Is there a way to point to the repositories CONTRIBUTING.md file?

Usually the projects have some specifics.

do they? In CDA we're missing the file entirely, but that could be an oversight on our end too 🙈

Maybe we can make the url overwritable then. If not specified pick the generic one as a fallback.

At least to me it would be odd getting such comment pointing to opensovd but I want the contribution guide from opensovd-cda/-core

probably would be best if each project just ships the file, if it's a carbon copy so be it, but it's also easier for newcomers to find it then. I'll make sure to fix this on cda side.

HosurSharanamma · 2026-06-10T08:07:06Z

Addressed all feedback:

Fixed copyright year from 2025 → 2026
Fixed workflow name from CI Checks → First Interaction (was conflicting with checks.yml)
Pinned runner from ubuntu-latest → ubuntu-24.04
@lh-sag @alexmohr for your review

alexmohr · 2026-06-16T12:51:41Z

  # pull-requests: write is required when post-pr-comment input is true.
-  # The caller workflow must grant this permission explicitly.
-  pull-requests: write
+# The caller workflow must grant this permission explicitly.


todo: please fix the indentation here.

Suggested change

# The caller workflow must grant this permission explicitly.

# The caller workflow must grant this permission explicitly.

@HosurSharanamma please do not resolve my review comments. I will resolve them myself when I re-reviewed. This one was resolved, but is not fixed yet. The indentation is still wrong.

alexmohr · 2026-06-16T12:53:04Z

-        if: >-
-          inputs.post-pr-comment && github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository
-        uses: actions/github-script@v9
+        if: ${{ inputs.post-pr-comment && github.event_name == 'pull_request' }}


question: these changes seem unrelated to the 'first interaction workflow' are these on purpose?

Thanks for hinting , those changes to coverage.yml were unrelate. I've removed them in the latest push.

I still see the changes in the diff, github fooling me or does this still need a push?

lh-sag · 2026-06-17T06:05:20Z

+          issue-message: |
+            Welcome, and thanks for opening your first issue!
+
+            Please make sure you've reviewed our [contribution guidelines](https://github.com/eclipse-opensovd/opensovd/blob/main/CONTRIBUTING.md)


Suggested change

Please make sure you've reviewed our [contribution guidelines](https://github.com/eclipse-opensovd/opensovd/blob/main/CONTRIBUTING.md)

Please make sure you've reviewed our [contribution guidelines](https://github.com/{{ github.repository_owner }}/${{ github.event.repository.name }}/blob/main/CONTRIBUTING.md)

@alexmohr would this work for you? Given that you add this file to cda.

@HosurSharanamma I am not sure whether this works. So feel free to experiment.

If that works that would be awesome.

Signed-off-by: sharanamma hosur <h.sharanamma@gmail.com>

Signed-off-by: HosurSharanamma <h.sharanamma@gmail.com>

alexmohr · 2026-08-05T11:55:11Z

  # pull-requests: write is required when post-pr-comment input is true.
-  # The caller workflow must grant this permission explicitly.
-  pull-requests: write
+# The caller workflow must grant this permission explicitly.


@HosurSharanamma please do not resolve my review comments. I will resolve them myself when I re-reviewed. This one was resolved, but is not fixed yet. The indentation is still wrong.

alexmohr · 2026-08-05T11:56:24Z

-        if: >-
-          inputs.post-pr-comment && github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository
-        uses: actions/github-script@v9
+        if: ${{ inputs.post-pr-comment && github.event_name == 'pull_request' }}


I still see the changes in the diff, github fooling me or does this still need a push?

coverage.yml was accidentally carrying stale/reverted content (missing pull-requests: write permission, older github-script version, bad comment indentation) unrelated to the first-interaction workflow. Restore it to match main exactly.

Apply the same dynamic link pattern already used in the issue-message to the pr-message, so forks/other orgs point to their own CONTRIBUTING.md instead of eclipse-opensovd/opensovd.

HosurSharanamma · 2026-09-22T08:48:25Z

coverage.yml is reverted back to match main exactly — the unrelated/stale content (missing pull-requests: write, wrong indentation, older github-script version) is gone. This PR now only touches first-interaction.yml.
The pr-message's CONTRIBUTING.md link is now dynamic (${{ github.repository_owner }}/${{ github.event.repository.name }}), matching the issue-message link fix from earlier, per @lh-sag's comment.

HosurSharanamma force-pushed the feat/add-first-interaction-workflow branch from 7e54798 to c872e62 Compare May 27, 2026 21:09

alexmohr reviewed May 28, 2026

View reviewed changes

Comment thread .github/workflows/first-interaction.yml Outdated

lh-sag mentioned this pull request May 29, 2026

ci: gradually adopt eclipse-opensovd/cicd-workflows shared workflows eclipse-opensovd/opensovd-core#79

Open

4 tasks

alexmohr previously approved these changes May 29, 2026

View reviewed changes

lh-sag requested changes May 29, 2026

View reviewed changes

HosurSharanamma force-pushed the feat/add-first-interaction-workflow branch from f06fdd6 to 4c0fb8c Compare June 10, 2026 07:52

HosurSharanamma dismissed alexmohr’s stale review via 95a029e June 10, 2026 08:01

HosurSharanamma force-pushed the feat/add-first-interaction-workflow branch from 4c0fb8c to 95a029e Compare June 10, 2026 08:01

HosurSharanamma mentioned this pull request Jun 10, 2026

chore: pin all workflows to specific ubuntu version instead of ubuntu-latest #55

Closed

alexmohr reviewed Jun 10, 2026

View reviewed changes

Comment thread .github/workflows/coverage.yml Outdated

alexmohr mentioned this pull request Jun 10, 2026

Improvement: Remove 'see contributors' from copyright headers #56

Closed

HosurSharanamma mentioned this pull request Jun 10, 2026

chore: pin all workflows to ubuntu-24.04 instead of ubuntu-latest #57

Merged

1 of 4 tasks

alexmohr reviewed Jun 11, 2026

View reviewed changes

Comment thread .github/workflows/coverage.yml Outdated

alexmohr reviewed Jun 11, 2026

View reviewed changes

Comment thread .github/workflows/first-interaction.yml Outdated

HosurSharanamma force-pushed the feat/add-first-interaction-workflow branch from 7d15c78 to 4db558c Compare June 16, 2026 10:00

HosurSharanamma requested review from alexmohr and lh-sag June 16, 2026 10:10

alexmohr requested changes Jun 16, 2026

View reviewed changes

HosurSharanamma force-pushed the feat/add-first-interaction-workflow branch 3 times, most recently from 96d7b33 to 4db558c Compare June 16, 2026 20:21

lh-sag reviewed Jun 17, 2026

View reviewed changes

HosurSharanamma mentioned this pull request Jul 27, 2026

Add first interaction workflow #73

Closed

4 tasks

HosurSharanamma added 4 commits July 27, 2026 11:18

feat: add first-interaction workflow for new contributors

6f7ae49

Signed-off-by: sharanamma hosur <h.sharanamma@gmail.com>

fix: revert actions/checkout to v6

1616935

Signed-off-by: sharanamma hosur <h.sharanamma@gmail.com>

fix: use dynamic repo owner/name in contribution guidelines link

f53ca97

Signed-off-by: HosurSharanamma <h.sharanamma@gmail.com>

fix: update license header to match REUSE format

868a998

Signed-off-by: HosurSharanamma <h.sharanamma@gmail.com>

HosurSharanamma force-pushed the feat/add-first-interaction-workflow branch from 718422d to 868a998 Compare July 29, 2026 08:36

HosurSharanamma requested a review from alexmohr July 29, 2026 08:37

alexmohr requested changes Aug 5, 2026

View reviewed changes

HosurSharanamma added 2 commits September 22, 2026 10:38

fix: use dynamic repo owner/name in pr-message CONTRIBUTING.md link

df30e27

Apply the same dynamic link pattern already used in the issue-message to the pr-message, so forks/other orgs point to their own CONTRIBUTING.md instead of eclipse-opensovd/opensovd.

		@@ -0,0 +1,45 @@
		# SPDX-License-Identifier: Apache-2.0
		# SPDX-FileCopyrightText: 2025 The Contributors to Eclipse OpenSOVD (see CONTRIBUTORS)

	# The caller workflow must grant this permission explicitly.
	# The caller workflow must grant this permission explicitly.

	Please make sure you've reviewed our [contribution guidelines](https://github.com/eclipse-opensovd/opensovd/blob/main/CONTRIBUTING.md)
	Please make sure you've reviewed our [contribution guidelines](https://github.com/{{ github.repository_owner }}/${{ github.event.repository.name }}/blob/main/CONTRIBUTING.md)

Conversation

HosurSharanamma commented May 27, 2026

Summary

Motivation

Changes

Testing

Uh oh!

alexmohr left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

alexmohr left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

lh-sag May 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lh-sag May 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

HosurSharanamma commented Jun 10, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

HosurSharanamma commented Sep 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

lh-sag May 29, 2026 •

edited

Loading

lh-sag May 29, 2026 •

edited

Loading