go-log4g/core

[madamovych]

Required links

Provide the links below. Our CI will automatically validate them.

• Forge link (github.com, gitlab.com, etc): https://github.com/go-log4g/core
• pkg.go.dev: https://pkg.go.dev/github.com/go-log4g/core
• goreportcard.com: https://goreportcard.com/report/github.com/go-log4g/core
• Coverage service link (codecov, coveralls, etc.): https://app.codecov.io/gh/go-log4g/core

Pre-submission checklist

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

Repository requirements

These are validated automatically by CI:

• The repo has a go.mod file and at least one SemVer release (vX.Y.Z).
• The repo has an open source license.
• The repo documentation has a pkg.go.dev link.
• The repo documentation has a goreportcard link (grade A- or better).
• The repo documentation has a coverage service link.

These are recommended and reported as warnings:

• The repo has a continuous integration process (GitHub Actions, etc.).
• CI runs tests that must pass before merging.

Pull Request content

These are validated automatically by CI:

• This PR adds/removes/changes only one package.
• The package has been added in alphabetical order.
• The link text is the exact project name.
• The description is clear, concise, non-promotional, and ends with a period.
• The link in README.md matches the forge link above.

Category quality

Note: new categories require a minimum of 3 packages.

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 they still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can describe a rule in plain language on the Rules page and Qodo drafts it for you

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

PR Summary by Qodo

Add go-log4g/core to Logging section

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Add go-log4g project link to the Logging libraries list.
• Document log4j-style configuration/pattern layouts support for Go log/slog.

High-Level Assessment

The change is a straightforward README index entry; no alternative technical approach is applicable beyond ensuring the link text, alphabetical placement, and description formatting meet repository contribution rules.

Files changed (1) +1 / -0

Documentation (1) +1 / -0

README.mdAdd go-log4g entry to Logging libraries list +1/-0

Add go-log4g entry to Logging libraries list

• Adds a new bullet under the Logging section linking to github.com/go-log4g/core. Includes a short description highlighting Log4j-style configuration and pattern layouts for Go's log/slog facade.

README.md

[qodo-code-review]

Qodo Fixer

No findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR.

[github-actions]

Automated Quality Checks

Required checks

✅ Repo: accessible, has go.mod and SemVer release
✅ pkg.go.dev: OK
✅ Go Report Card: OK (grade unknown)

Additional checks

✅ License: Apache-2.0
⚠️ Maturity: repo appears to have less than 5 months of history

How to fix: Your repository needs at least 5 months of history since the first commit.
Please resubmit after the repository meets this requirement.
⚠️ CI/CD: no GitHub Actions workflows found
How to fix: Add a CI workflow to run tests automatically.
Create .github/workflows/test.yml — see https://docs.github.com/en/actions/use-cases-and-examples/building-and-testing/building-and-testing-go
✅ README: present
⚠️ Coverage: missing from PR body
How to fix: Add a coverage service link to your PR description:

Coverage: https://app.codecov.io/gh/your-org/your-project

Popular options: [Codecov](https://codecov.io), [Coveralls](https://coveralls.io). Integrate one with your CI to track coverage automatically.


_These checks are automated and do not replace maintainer review. See [CONTRIBUTING.md](https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md) for full guidelines._

---

## PR Diff Validation

### Content checks

✅ **Files changed**: only README.md
✅ **Single item**: one package added
✅ **Link consistency**: README link matches forge link in PR body
✅ **Description**: ends with punctuation
✅ **Description tone**: no promotional language detected
✅ **Category size**: Logging has 66 items

### Warnings

⚠️ **Link text**: `go-log4g` differs from repo name `core`
  > **How to fix:** The link text should be the exact project name.
  > If the project name really is `go-log4g`, this is fine. Otherwise change it to: `- [core](https://github.com/go-log4g/core) - ...`


_Automated diff validation — does not replace maintainer review._
<!-- Sticky Pull Request Commentpr-quality-check -->