Skip to content

Initialize JetBrains Junie 🚀 #1

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

jetbrains-junie[bot]
Copy link

@jetbrains-junie jetbrains-junie bot commented Jul 23, 2025

This PR initializes JetBrains Junie 🚀 by adding essential configuration files.

Includes:

  • GitHub workflow for automated execution
  • Dev container setup (if applicable)
  • Language-specific scripts (if applicable)

Generated automatically by Junie. Review and customize as needed.

Summary by Sourcery

Initialize JetBrains Junie by adding essential configuration files for automated workflows and development environment

Enhancements:

  • Add Junie GitHub Actions workflow to dispatch and invoke jetbrains-junie/junie-workflows with input parameters
  • Include .devcontainer/devcontainer.json for consistent development container setup

Copy link

sourcery-ai bot commented Jul 23, 2025

Reviewer's Guide

This PR bootstraps JetBrains Junie by programmatically adding a custom GitHub Actions workflow for manual invocation and setting up a development container configuration to standardize the dev environment.

File-Level Changes

Change Details Files
Add GitHub Actions workflow to trigger Junie runs
  • Create junie.yml under .github/workflows
  • Configure workflow_dispatch inputs for run_id and workflow_params
  • Grant write permission to contents
  • Invoke external Junie workflow with passed parameters
.github/workflows/junie.yml
Introduce devcontainer configuration for consistent environments
  • Add devcontainer.json in .devcontainer directory
  • Define container settings and extensions (auto-generated default)
.devcontainer/devcontainer.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

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.

0 participants