Skip to content

Commit f644c77

Browse files
committed
feat: add best practices
1 parent 5d806d1 commit f644c77

File tree

3 files changed

+34
-1
lines changed

3 files changed

+34
-1
lines changed

lib/algora/bot_templates/bot_templates.ex

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,12 @@ defmodule Algora.BotTemplates do
1212
2. **Submit work**: Create a pull request including `/claim #${ISSUE_NUMBER}` in the PR body to claim the bounty
1313
3. **Receive payment**: 100% of the bounty is received 2-5 days post-reward. [Make sure you are eligible for payouts](https://algora.io/docs/payments#supported-countries-regions)
1414
15+
### ❗ Important guidelines:
16+
- To claim a bounty, you need to **provide a short demo video** of your changes in your pull request
17+
- If anything is unclear, **ask for clarification** before starting as this will help avoid potential rework
18+
- Low quality AI PRs will not receive review and will be closed
19+
- Do not ask to be assigned unless you've contributed before
20+
1521
Thank you for contributing to ${REPO_FULL_NAME}!
1622
${ATTEMPTS}
1723
"""

lib/algora_web/live/docs_live.ex

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,8 @@ defmodule AlgoraWeb.DocsLive do
88
title: "Overview",
99
links: [
1010
%{title: "Introduction", href: "/docs"},
11-
%{title: "Slash commands", href: "/docs/commands"}
11+
%{title: "Slash commands", href: "/docs/commands"},
12+
%{title: "Best practices", href: "/docs/best-practices"}
1213
]
1314
},
1415
%{
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
title: Best practices
3+
---
4+
5+
# Best practices
6+
7+
## Issue specs
8+
9+
Good issue specs are the recipe for success.
10+
11+
Explain in detail the desired outcome, any limitations and the acceptance criteria. Include references, examples and mockups where applicable.
12+
13+
- "It should abide by our code styles" is not a requirement and is extremely vague, has no clarity in communication
14+
- "It should do X, while we don't want Y, we could ignore if it does Z, but definitely shouldn't do K" is the correct approach
15+
16+
Explain technical requirements to work on the issue, ex "Our project requires Mac, with at least this amount of RAM"
17+
18+
## PR review
19+
20+
- Require devs to demonstrate via screenshot/recording that at least X, Y, Z was accomplished to get PR review
21+
- Close low quality AI PRs without review
22+
- Do not assign developers without a contribution history
23+
24+
## References
25+
26+
- [Golem Cloud](https://algora.io/golemcloud/home), [Deskflow](https://algora.io/deskflow/home) and [Remotion](https://algora.io/remotion/home) have been praised by developers for writing the best specs

0 commit comments

Comments
 (0)