Skip to content

docs: add PRs welcome badge and good first issues link - #550

Open
ayoolaowoilu wants to merge 2 commits into
ever-co:developfrom
ayoolaowoilu:patch-1
Open

ayoolaowoilu wants to merge 2 commits into
ever-co:developfrom
ayoolaowoilu:patch-1

Conversation

@ayoolaowoilu

@ayoolaowoilu ayoolaowoilu commented Jul 16, 2026

Copy link
Copy Markdown

Added a badge for PRs welcome to the README.

Before submitting the PR, please make sure you do the following

  1. Contributor license agreement
    For us it's important to have the agreement of our contributors to use their work, whether it be code or documentation. Therefore, we are asking all contributors to sign a contributor license agreement (CLA) as commonly accepted in most open source projects. Just open the pull request and our CLA bot will prompt you briefly.

  2. Please check our contribution guidelines for some help in the process.


Summary by cubic

Adds a “PRs welcome” badge to the README and a “good first issues” link in the contribution section to make it easier for new contributors to get started.

Written for commit c717b78. Summary will update on new commits.

Review in cubic

Added a badge for PRs welcome to the README.
@cla-assistant

cla-assistant Bot commented Jul 16, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@cla-assistant

cla-assistant Bot commented Jul 16, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@greptile-apps

greptile-apps Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds a "PRs Welcome" badge to the top of the README and a "good first issues" link in the contributing section, making it easier for newcomers to find entry points.

  • The badge image is sourced from shields.io over HTTPS, but its click-through target points to http://makeapullrequest.com rather than https://, which is inconsistent with every other badge link in the file.
  • The "good first issues" link correctly targets the filtered GitHub issues view and is a useful addition to the contributing guidance.

Confidence Score: 5/5

Documentation-only change; safe to merge after fixing the HTTP link.

Both additions are purely textual changes to the README. The only notable issue is the badge's click-through URL using http:// instead of https://, which could produce a mixed-content warning but has no functional impact on the project itself.

README.md — only for the HTTP vs HTTPS badge URL.

Important Files Changed

Filename Overview
README.md Adds a "PRs Welcome" badge and a "good first issues" link to the contributing section; badge target uses HTTP instead of HTTPS.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[README.md badge row] --> B["PRs Welcome badge\n(shields.io image, http target)"]
    C[Contributing section] --> D["Good first issues link\n(GitHub filtered issues)"]
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[README.md badge row] --> B["PRs Welcome badge\n(shields.io image, http target)"]
    C[Contributing section] --> D["Good first issues link\n(GitHub filtered issues)"]
Loading

Reviews (1): Last reviewed commit: "Add PRs welcome badge to README" | Re-trigger Greptile

Comment thread README.md Outdated
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

The README adds a PRs-welcome badge and a contribution link for finding good first issues.

Changes

Contributor guidance

Layer / File(s) Summary
README contribution guidance
README.md
Adds a PRs-welcome badge and a “good first issues” link under the Contribute section.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: evereq

Poem

A bunny sees a badge shine bright,
And finds first issues left just right.
With hops and paws, contributors near,
The README makes the path more clear.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly matches the README updates for the PRs welcome badge and good first issues link.
Description check ✅ Passed The description is directly related to the README contribution updates described in the changeset.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands.

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
@sonarqubecloud

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 8: Update the PRs Welcome badge link in README.md to point to the
repository’s contribution guide, replacing the unrelated makeapullrequest.com
destination while preserving the existing badge image and label.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: f9712b21-fb09-487f-859e-da08aa35dcfd

📥 Commits

Reviewing files that changed from the base of the PR and between 9b04d47 and 22d03f3.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
[![GitHub License](https://img.shields.io/badge/license-AGPL-v3.svg)](https://raw.githubusercontent.com/ever-co/ever-traduora/master/LICENSE)
[![Docker Pulls](https://img.shields.io/docker/pulls/traduora/traduora)](https://hub.docker.com/r/traduora/traduora)
[![Get help on Codementor](https://cdn.codementor.io/badges/get_help_github.svg)](https://www.codementor.io/evereq?utm_source=github&utm_medium=button&utm_term=evereq&utm_campaign=github)
[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://makeapullrequest.com)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

Point the badge to the repository’s contribution guide.

The current destination is an unrelated conference site containing promotional content, not a pull-request guide. This makes the contributor entry point misleading and potentially unsafe. (makeapullrequest.com)

Proposed fix
-[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://makeapullrequest.com)
+[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/ever-co/ever-traduora/blob/develop/.github/CONTRIBUTING.md)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://makeapullrequest.com)
[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/ever-co/ever-traduora/blob/develop/.github/CONTRIBUTING.md)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 8, Update the PRs Welcome badge link in README.md to point
to the repository’s contribution guide, replacing the unrelated
makeapullrequest.com destination while preserving the existing badge image and
label.

Source: MCP tools

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 1 file

Re-trigger cubic

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.

1 participant