OSOE-726: Migrate auto-resolve-done-jira-issue and create-jira-issues-for-community-activities to use API Key Manager for Jira in Lombiq.GitHub.Actions

[Piedone]

OSOE-726

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflows to use specific issue or commit references.
  • Replaced old JIRA-related secrets with new ones for improved integration.
• Refactor
  • Updated submodule reference for Lombiq.GitHub.Actions to the latest commit.

[Piedone]

@coderabbitai review

[coderabbitai]

Note

Reviews Paused

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Walkthrough

The workflow files have been updated to reference specific issues or commits, enhancing precision in automation. The integration with JIRA has been refined, switching from general secrets to more specific endpoint URLs and API keys, reflecting a more secure and streamlined approach to project management automation. The submodule for GitHub actions has also been updated to a new commit, indicating improvements or fixes in the actions used.

Changes

File Path	Change Summary
.github/workflows/.../build-and-test-windows.yml .github/workflows/.../build-and-test.yml .github/workflows/.../create-jira-issues-for-community-activities.yml	Updated uses field to reference specific issues/commits; replaced JIRA secrets with JIRA_ENDPOINT_URL and JIRA_API_KEY.
tools/.../Lombiq.GitHub.Actions	Updated submodule commit reference.

Poem

🐇✨
In the burrow of code, under moon's soft glow,
The rabbit hopped through, refining the flow.
With secrets secured and references tight,
The workflows now dance, in the deep tech night. 🌙💻

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• You can directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• You can tag CodeRabbit on specific lines of code or entire files in the PR by tagging @coderabbitai in a comment. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• You can tag @coderabbitai in a PR comment and ask questions about the PR and the codebase. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid.
  • @coderabbitai read the files in the src/scheduler package and generate README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 680d512 and 0edcd68.

Files selected for processing (4)

• .github/workflows/build-and-test-windows.yml (1 hunks)
• .github/workflows/build-and-test.yml (1 hunks)
• .github/workflows/create-jira-issues-for-community-activities.yml (1 hunks)
• tools/Lombiq.GitHub.Actions (1 hunks)

Files skipped from review due to trivial changes (3)

• .github/workflows/build-and-test-windows.yml
• .github/workflows/create-jira-issues-for-community-activities.yml
• tools/Lombiq.GitHub.Actions

Additional comments: 2

.github/workflows/build-and-test.yml (2)

• 76-76: The uses field in the "Post Pull Request Checks Automation" job has been updated to reference @issue/OSOE-726 instead of @dev. Verify that referencing an issue is intentional and confirm that it will not affect the availability or functionality of the workflow.

• 78-79: The JIRA-related secrets have been updated to JIRA_ENDPOINT_URL and JIRA_API_KEY. Ensure that these new secrets are correctly configured in the repository's secrets settings and that they are compatible with the updated GitHub Actions.

[Piedone]

@coderabbitai pause

[github-actions]

This pull request has merge conflicts. Please resolve those before requesting a review.

[Piedone]

We can't continue with this, see Lombiq/GitHub-Actions#277 (comment).