rosslh/coolify
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(repo): remove bounty and beta referrences on contributors guidelines

Browse source
This commit is contained in:
ShadowArcanist 2026-06-13 20:24:44 +05:30
parent 7b5415fdbe
commit 62d9e40186
No known key found for this signature in database
1 changed files with 7 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
CONTRIBUTING.md
View file

@ -27,14 +27,14 @@ ## High-Level Expectations
## State of the Project
Coolify is currently at v4 and is still in beta. While v4 is stable, it has some limitations, including:
Coolify is currently at v4. While v4 is stable, it has some limitations, including:
- Limited scaling support
- A more complex user experience
- Other smaller issues that need refinement
These limitations will be addressed in Coolify v5, which is in the planning stage. However, the maintainers are focused on releasing a stable v4 version before dedicating time to v5 development. Because of this, major features, architectural changes, or significant UI changes will not be accepted for v4 at this stage.
These limitations will be addressed in Coolify v5, which is in the planning stage. Because of this, major features, architectural changes, or significant UI changes will not be accepted for v4 at this stage.
We welcome contributions that help stabilize v4, but larger changes will be saved for v5 once we have a stable v4 release.
We welcome contributions that help stabilize v4 for a bug free experience.
## What Makes a Strong Contribution
@ -122,7 +122,7 @@ ## 2. Bug Report Contributions
- Expected result
- Actual result
Incomplete reports may be closed.
Incomplete reports and reports generated using AI may be closed.
## 3. Code Contributions
@ -177,7 +177,7 @@ ## AI Usage Disclosure
## Test Before Submitting
Before submitting a pull request:
- Test your changes thoroughly
- Manually test your changes thoroughly
- Verify they work in a clean environment
- Provide detailed testing steps in the PR description
@ -186,22 +186,12 @@ ## Test Before Submitting
## Submitting a Pull Request
- GitHub will auto-populate the PR template
- The contributor agreement must remain intact
- The contributor agreement in PR description must remain intact
- Pull requests without the contributor agreement will be closed
- All pull requests must target the `next` branch
- PRs targeting other branches will be closed without review
## Bounty Issues
Community members may create bounty issues for features or improvements.
Important:
- Only existing contributors are eligible
- First-time contributors targeting bounty issues will be automatically closed and maybe excluded from contributing.
This policy exists to prevent spam. We close 30+ bounty-targeted spam PRs per week.
## FAQ
**Q: Should I ask before fixing a typo or a small bug?**
A: No, small, obvious fixes like typos or narrowly-scoped bug fixes can be submitted as a PR directly.
@ -210,7 +200,7 @@ ## FAQ
A: Awesome! Discuss it first in GitHub Discussions or Discord. **Do not** open a PR for new features without prior alignment.
**Q: My PR was closed without detailed feedback.**
A: This usually means it didn’t align with the project’s direction, required more review bandwidth than available, or targeted major changes not allowed in v4. This is normal for a two-maintainer project.
A: This usually means it didn’t align with the project’s direction, required more review bandwidth than available, or targeted major changes not allowed in v4.
**Q: Can I work on an open issue?**
A: Comment on the issue first to confirm it’s still relevant and that no one else is actively working on it. For anything beyond a small fix, discuss your approach before implementing.
@ -221,9 +211,6 @@ ## FAQ
**Q: Can I use AI to help with my PR?**
A: Yes, AI-assisted contributions are allowed. But you must fully understand and verify the changes. PRs that appear to be generated by AI without context understanding will be closed.
**Q: Can I work on a bounty issue as a first-time contributor?**
A: No, bounty issues are reserved for existing contributors. First-time contributors targeting bounty issues will have their PRs closed without review. This prevents spam and ensures bounties go to contributors familiar with the project.
**Q: My PR was closed without review. Can I submit a new one?**
A: Yes, but keep in mind a PR closure is feedback, not a rejection of your effort. It usually means the PR didn’t match the project goals or guidelines. Address these issues first — repeating the same approach may hurt your standing with maintainers.