Fix action directory layout

[leynos]

Summary

• move export-postgres-url action into .github/actions
• move generate-coverage action into .github/actions
• update paths in README

Testing

• npm test (fails: could not find package.json)

---

https://chatgpt.com/codex/tasks/task_e_68529041fe948322a38ab99a181d71c2

Summary by Sourcery

Organize custom actions under .github/actions and align documentation accordingly.

Enhancements:

• Relocate export-postgres-url action into .github/actions/export-postgres-url
• Relocate generate-coverage action into .github/actions/generate-coverage

Documentation:

• Update README to reflect new action directory paths

Summary by CodeRabbit

• Documentation
  • Updated the README to reflect new paths for the "Export Postgres URL" and "Generate coverage" GitHub Actions.

[sourcery-ai]

Reviewer's Guide

Reorganized two custom GitHub Actions by moving their directories into .github/actions and updated the README table to point to the new locations.

File-Level Changes

Change	Details	Files
Relocate custom action directories into a single folder	Move export-postgres-url action directory into .github/actions Move generate-coverage action directory into .github/actions	.github/export-postgres-url .github/generate-coverage .github/actions/export-postgres-url .github/actions/generate-coverage
Update README to reflect new action paths	Adjust Export Postgres URL path entry to .github/actions/export-postgres-url Adjust Generate coverage path entry to .github/actions/generate-coverage	README.md

---

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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Walkthrough

The README file was updated to reflect new paths for the "Export Postgres URL" and "Generate coverage" GitHub Actions, changing their directory references to include an additional "actions" subfolder. No other modifications were made to the content or structure of the README.

Changes

File	Change Summary
README.md	Updated GitHub Actions paths for "Export Postgres URL" and "Generate coverage" to new locations

Poem

In README’s warren, paths did shift,
Actions now in “actions” nest,
Postgres and coverage, tidy and swift,
Their new burrows clearly expressed.
With every hop, our docs stay neat—
A rabbit’s touch makes change complete! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8121c9e and d010896.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (1)

README.md (1)

8-9: Action paths updated to new directory layout.

The entries now correctly reference the actions subdirectory under .github.

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch codex/fix-.github-layout-and-structure

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

Hey @leynos - I've reviewed your changes - here's some feedback:

• Update any workflow YAML files under .github/workflows to point to the new .github/actions/<action> paths so the moved actions continue to be used.
• Address the failing npm test error by ensuring a package.json is present or by updating test configurations to reflect the new directory structure.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Update any workflow YAML files under `.github/workflows` to point to the new `.github/actions/<action>` paths so the moved actions continue to be used.
- Address the failing `npm test` error by ensuring a `package.json` is present or by updating test configurations to reflect the new directory structure.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}