Skip to content

DEVOPS-989: use reusable pr_jira_actions workflow#54

Open
andrewg-mira wants to merge 1 commit intodevelopfrom
DEVOPS-989-github-PR-action
Open

DEVOPS-989: use reusable pr_jira_actions workflow#54
andrewg-mira wants to merge 1 commit intodevelopfrom
DEVOPS-989-github-PR-action

Conversation

@andrewg-mira
Copy link
Contributor

@andrewg-mira andrewg-mira commented Mar 11, 2026

DEVOPS-989 - Migrate repositories to use Jira actions github workflow

Copilot AI review requested due to automatic review settings March 11, 2026 17:07
@github-actions github-actions bot changed the title DEVOPS-989 use reusable pr_jira_actions workflow DEVOPS-989: use reusable pr_jira_actions workflow Mar 11, 2026
Copy link

Copilot AI 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 overview

Updates the repository’s PR-to-JIRA automation workflow to use the newer reusable pr_actions workflow, aligning triggers with other PR workflows.

Changes:

  • Renames the workflow and switches to MiraGeoscience/CI-tools/.github/workflows/reusable-jira-pr_actions.yml@v3.
  • Expands PR event triggers to include synchronize, reopened, and ready_for_review.
  • Reorders the passed JIRA secrets (no functional change).
Comments suppressed due to low confidence (1)

.github/workflows/pr_jira_actions.yml:6

  • This workflow no longer sets a top-level permissions: {}. In this repo, other workflows consistently set workflow-level permissions to {} and then explicitly grant per-job permissions (e.g., .github/workflows/python_analysis.yml:20, issue_to_jira.yml:7). Consider re-adding permissions: {} at the workflow level here to keep the default GITHUB_TOKEN scope minimal and consistent, while relying on the job-level permissions block for the required access.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

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