Skip to content

fix: strip spaces and newlines from the comment before matching #1924

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

chmouel
Copy link
Member

@chmouel chmouel commented Feb 11, 2025

We are now stripping spaces and newlines from the beginning and the end to make sure that the regex matches correctly. The ^ will match the beginning of the comment and $ will match the end of the comment without newlines or space.

Changes

Submitter Checklist

  • 📝 Ensure your commit message is clear and informative. Refer to the How to write a git commit message guide. Include the commit message in the PR body rather than linking to an external site (e.g., Jira ticket).

  • ♽ Run make test lint before submitting a PR to avoid unnecessary CI processing. Consider installing pre-commit and running pre-commit install in the repository root for an efficient workflow.

  • ✨ We use linters to maintain clean and consistent code. Run make lint before submitting a PR. Some linters offer a --fix mode, executable with make fix-linters (ensure markdownlint and golangci-lint are installed).

  • 📖 Document any user-facing features or changes in behavior.

  • 🧪 While 100% coverage isn't required, we encourage unit tests for code changes where possible.

  • 🎁 If feasible, add an end-to-end test. See README for details.

  • 🔎 Address any CI test flakiness before merging, or provide a valid reason to bypass it (e.g., token rate limitations).

    (update the documentation accordingly)

We are now stripping spaces and newlines from the beginning and the end to make
sure that the regex matches correctly. The ^ will match the beginning of the
comment and $ will match the end of the comment without newlines or space.

Signed-off-by: Chmouel Boudjnah <[email protected]>
@zakisk
Copy link
Contributor

zakisk commented Feb 13, 2025

/lgtm

Copy link

@pipelines-as-code pipelines-as-code bot left a comment

Choose a reason for hiding this comment

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

✅ Pull Request Approved

Approval Status:

  • Required Approvals: 1
  • Current Approvals: 1

👥 Approved By:

Reviewer Permission Status
@zakisk admin

📝 Next Steps

  • All required checks must pass
  • Branch protection rules apply
  • Get a maintainer to use the /merge command to merge the PR

Thank you for your contributions! 🎉

@chmouel
Copy link
Member Author

chmouel commented Feb 13, 2025

/merge

@pipelines-as-code pipelines-as-code bot merged commit 7051c93 into openshift-pipelines:main Feb 13, 2025
7 checks passed
Copy link

✅ PR Successfully Merged

  • Merge method: rebase
  • Merged by: @chmouel
  • Total approvals: 1/1

Approvals Summary:

Reviewer Permission Status
@zakisk admin

@chmouel chmouel deleted the fix-strip-spaces-and-newlines-from-the-comment-bef branch February 13, 2025 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants