Skip to content

Conversation

@CGastrell
Copy link
Contributor

Proposed changes:

  • Add instruction to navigate back to root repo directory after running the changelogger command
  • This fixes an issue where subsequent commands would fail because the working directory was still in the project subdirectory

Other information:

  • Have you written new tests for your changes, if applicable? N/A - documentation only
  • Have you checked the E2E test CI results, and verified that your changes do not break them? N/A
  • Have you tested your changes on WordPress.com, if applicable? N/A

Jetpack product discussion

N/A - Developer tooling improvement

Does this pull request change what data or activity we track or use?

No

Testing instructions:

  • Run /jetpack-changelog in Claude Code on a branch with project changes
  • Verify the command now includes step 5 to navigate back to root repo directory
  • Confirm that after running the command, you are back in the repo root (not stuck in a project subdirectory)

@CGastrell CGastrell added [Status] Needs Review This PR is ready for review. [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it labels Dec 23, 2025
@CGastrell CGastrell self-assigned this Dec 23, 2025
@CGastrell CGastrell added the Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR label Dec 23, 2025
@github-actions
Copy link
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

Copy link
Contributor

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

This PR improves the jetpack-changelog Claude command by adding an instruction to navigate back to the root repository directory after running the changelogger command, preventing subsequent commands from failing due to being in a project subdirectory.

Key Changes:

  • Adds step 5 to navigate back to the root repo directory
  • Renumbers the git staging step from 5 to 6

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

--entry="{description}"
```
5. Stage the generated changelog file with `git add`
5. Navigate back to root repo directory
Copy link

Copilot AI Dec 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The instruction to navigate back to the root directory should include the actual command to execute, similar to how other steps provide explicit commands. Consider specifying the command, such as using cd - to return to the previous directory, or cd ../.. or similar depending on the typical project depth.

Suggested change
5. Navigate back to root repo directory
5. Navigate back to root repo directory: `cd -`

Copilot uses AI. Check for mistakes.
@CGastrell CGastrell requested a review from lezama December 23, 2025 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR [Status] Needs Review This PR is ready for review. [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants