Description of problem:

Currently, any changes to the rhdh_jira_lint.py script, when committed to the main branch, immediately trigger a GitLab pipeline that sends real Slack messages to all affected users. This results in noisy and unintended notifications during development and testing.

This issue introduces a dry-run mode controlled by environment variables (DRY_RUN and TEST_USER_EMAIL) that:

• Prevents Slack API calls by printing messages instead

• Limits Jira processing to a specific test user (e.g., fndlovu@redhat.com)

• Allows manual pipeline triggering via GitLab UI with a DRY_RUN flag

• Keeps scheduled pipelines intact for production use

CI/CD behavior is updated to prevent accidental Slack messages on push to main.

Acceptance Criteria:

• Script supports a DRY_RUN=true mode that skips all Slack API calls and prints what would be sent

• Script allows setting TEST_USER_EMAIL to limit Jira results

• GitLab job is configured to:

• • Run only when scheduled or manually triggered

• • Respect the DRY_RUN environment variable

• Running the job with DRY_RUN=true on main does not send any Slack messages

• Scheduled pipelines continue sending real messages

• Updated documentation is available for local testing and GitLab manual pipeline usage