Add jkaninda/pg-bkup

[jkaninda]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/jkaninda/pg-bkup
• pkg.go.dev: https://pkg.go.dev/github.com/jkaninda/pg-bkup
• goreportcard.com: https://goreportcard.com/report/github.com/jkaninda/pg-bkup
• coverage service link (codecov, coveralls, etc.):

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.
• I removed the following packages around my addition: (please give a short reason for each removal)

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Added information about pg-bkup, a PostgreSQL backup, restore, and migration tool with multiple storage backends and GPG encryption support.

[coderabbitai]

Walkthrough

A new PostgreSQL backup and migration tool entry (pg-bkup) was added to the README's "Software Packages" section. The addition describes a tool supporting multiple storage backends and GPG encryption for backup, restore, and migration operations.

Changes

Cohort / File(s)	Change Summary
Documentation Update README.md	Added pg-bkup entry to "Software Packages" section between ostent and PipeCD items

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• The change is a straightforward documentation addition with no logic, code, or structural modifications

Poem

🐰 A tool for backups, now in our tome,
With PostgreSQL treasures safe at home,
Through GPG vaults and storage wide,
pg-bkup joins with rabbit pride! 📚✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Add jkaninda/pg-bkup" is fully related to the main change in the pull request, which is adding a new PostgreSQL backup tool entry to the Software Packages section of the README. The title is concise and specific, clearly identifying the package being added without unnecessary noise. A teammate scanning the PR history would immediately understand that this PR introduces a new package listing to the awesome-go repository. The title directly reflects the primary change and meets the criteria for clarity and specificity.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

3379-3379: Minor wording polish for neutrality and style.

Looks good: correct section, alphabetical placement, and description ends with a period. To better match Awesome list tone, consider a more neutral/concise phrasing (lowercase “local”, use “backends”):

- - [pg-bkup](https://github.com/jkaninda/pg-bkup) - PostgreSQL backup, restore, and migration tool with support for Local, S3, FTP, SFTP, and Azure Blob Storage ensuring data security through GPG encryption.
+ - [pg-bkup](https://github.com/jkaninda/pg-bkup) - PostgreSQL backup, restore, and migration tool with local, S3, FTP, SFTP, and Azure Blob Storage backends, plus optional GPG encryption.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 44263fc and 461745e.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

README.md

📄 CodeRabbit inference engine (AGENTS.md)

README.md: When modifying the Awesome list, keep categories with at least three entries
Descriptions in the Awesome list must end with a period
Avoid promotional copy; keep descriptions concise and neutral in the Awesome list
Do not remove existing list content unless removal is requested and justified

Files:

• README.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• README.md

{README.md,COVERAGE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Align rendered documentation (README.md, COVERAGE.md, etc.) with behavior changes in main.go or helper packages

Files:

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: quality

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: OK
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: missing

These checks are a best-effort automation and do not replace human review.