Skip to content

Conversation

@Igor-splunk
Copy link
Collaborator

Description

What does this PR have in it?

Key Changes

Highlight the updates in specific files

Testing and Verification

How did you test these changes? What automated tests are added?

Related Issues

Jira tickets, GitHub issues, Support tickets...

PR Checklist

  • Code changes adhere to the project's coding standards.
  • Relevant unit and integration tests are included.
  • Documentation has been updated accordingly.
  • All tests pass locally.
  • The PR description follows the project's guidelines.

@coveralls
Copy link
Collaborator

coveralls commented Dec 9, 2025

Pull Request Test Coverage Report for Build 20303360958

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 86.371%

Totals Coverage Status
Change from base Build 20029264179: 0.0%
Covered Lines: 10729
Relevant Lines: 12422

💛 - Coveralls

@kasiakoziol kasiakoziol self-requested a review December 10, 2025 06:17
Copy link
Collaborator

@patrykw-splunk patrykw-splunk left a comment

Choose a reason for hiding this comment

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

LGTM!

@Igor-splunk Igor-splunk changed the base branch from develop to main December 11, 2025 08:25
@kubabuczak
Copy link
Collaborator

why MR to main directly?

env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# The below token should have repo scope and must be manually added by a maintainer in the GitHub Secrets
PERSONAL_ACCESS_TOKEN: ${{ secrets.CLA_ASSISTANT_PAT }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Did you add this secret? I don't see it in our secrets in GitHub.
What is the TTL of this PAT? Should we track and manage expiration date?

Copy link
Collaborator

@kubabuczak kubabuczak left a comment

Choose a reason for hiding this comment

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

I would say that we should merge it to develop.
Do you have an example of execution of this workflow?


# the following fields are optional
remote-organization-name: splunk
remote-repository-name: splunk-operator-cla-signatures
Copy link
Collaborator

Choose a reason for hiding this comment

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

where is this repository?

@Igor-splunk Igor-splunk changed the base branch from main to develop December 11, 2025 15:52
uses: cla-assistant/github-action@v2.1.3-beta
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
PERSONAL_ACCESS_TOKEN: ${{ secrets.PAT_CLATOOL }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Did you create this secret? I don't see it in our secrets.

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.

5 participants