Skip to content
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

ci(commitlint): check for the presence of concrete PR number #29

Merged
merged 2 commits into from
Feb 8, 2024

Conversation

tiborsimko
Copy link
Member

  • ci(commitlint): check for the presence of concrete PR number

    Enrich commitlint checker in order to check the precise PR number in the
    commit log headline.

  • ci(shellcheck): fix exit code propagation

    Return properly the exit code status of shellcheck command when looping
    through shell script files.

tiborsimko added a commit to tiborsimko/reana-demo-cms-h4l that referenced this pull request Jan 26, 2024
Return properly the exit code status of shellcheck command when looping
through shell script files.
tiborsimko added a commit to tiborsimko/reana-demo-cms-h4l that referenced this pull request Jan 26, 2024
…b#29)

Enrich commitlint checker in order to check the precise PR number in the
commit log headline.
@tiborsimko tiborsimko force-pushed the ci-commitlint-shellcheck branch from 62ddc94 to 54b9592 Compare January 26, 2024 09:12
Return properly the exit code status of shellcheck command when looping
through shell script files.
…b#29)

Enrich commitlint checker in order to check the precise PR number in the
commit log headline.
@tiborsimko tiborsimko force-pushed the ci-commitlint-shellcheck branch from 54b9592 to 00823d0 Compare February 8, 2024 12:58
@tiborsimko tiborsimko merged commit 00823d0 into reanahub:master Feb 8, 2024
3 checks passed
@tiborsimko tiborsimko deleted the ci-commitlint-shellcheck branch February 8, 2024 13:00
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.

2 participants