Skip to content

Commit 7e84b10

Browse files
committed
add buddy check template
1 parent 280b14a commit 7e84b10

File tree

1 file changed

+43
-0
lines changed

1 file changed

+43
-0
lines changed
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
name: Buddy Exchange Request
3+
about: Request a new buddy exchange for a CODECHECK
4+
title: '[Author Name] | [CHECK-IDENTIFIER] '
5+
labels: ['buddy exchange']
6+
---
7+
8+
**Brief Description:**
9+
<!-- Provide a brief description of your project or the area you need help with -->
10+
11+
**Code Repository:**
12+
<!-- Provide a link to your code repository (GitHub, GitLab, etc.) -->
13+
14+
**Data Repository (if applicable):**
15+
<!-- Provide a link to your data repository or dataset -->
16+
17+
**Published Paper or Preprint:**
18+
<!-- Provide a link to your published paper or preprint, ideally with a DOI -->
19+
20+
**What You Can Offer:**
21+
<!-- Describe what you can offer in return (your expertise, code review, etc.) -->
22+
23+
**Timeline:**
24+
<!-- When do you need this collaboration? Any deadlines? -->
25+
26+
**Additional Information:**
27+
<!-- Any other relevant details -->
28+
29+
<!--
30+
31+
**Next Steps:**
32+
33+
1. After submitting this issue, check the [buddy-exchange label](https://github.com/daniel/buddy-exchange/labels/buddy-exchange) to see all active requests to find potential matches
34+
2. To find your issue ID, look at current issues labeled "id assigned"
35+
36+
**Guidelines:**
37+
38+
- Be specific about what you're looking for
39+
- Include links to public repositories when possible
40+
- Be clear about timelines and expectations
41+
- Tag relevant technologies or domains in your description
42+
43+
-->

0 commit comments

Comments
 (0)