Skip to content

fix: test codex review#507

Open
mkolasinski-splunk wants to merge 1 commit into
developfrom
mkolasinski-splunk-patch-1
Open

fix: test codex review#507
mkolasinski-splunk wants to merge 1 commit into
developfrom
mkolasinski-splunk-patch-1

Conversation

@mkolasinski-splunk

Copy link
Copy Markdown
Contributor

Description

(PR description goes here)

Checklist

  • README.md has been updated or is not required
  • push trigger tests
  • manual release test
  • automated releases test
  • pull request trigger tests
  • schedule trigger tests
  • workflow errors/warnings reviewed and addressed

Testing done

(for each selected checkbox, the corresponding test results link should be listed here)

@mkolasinski-splunk mkolasinski-splunk requested a review from a team as a code owner June 25, 2026 08:49

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 834edf738f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 2 to 3
on:
push:
branches:
- "main"
- "develop"
tags:
- "v[0-9]+.[0-9]+.[0-9]+"
pull_request:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore the push triggers for releases

With this workflow now subscribed only to pull_request, merges to main/develop and v* tag pushes no longer start the only self-release workflow. The publish job below invokes semantic-release, and update-semver is gated on refs/tags/v, while README.md lines 160-175 describe releases being produced after merging to main; after this change those events are never delivered, so releases and semver tag updates stop.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant