You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,20 +104,20 @@ docs/
104
104
105
105
### Submission Process
106
106
107
-
#### For Small Changes
108
-
1. Fork the repository
109
-
2. Create a feature branch: `git checkout -b fix/update-documentation`
110
-
3. Make your changes
111
-
4. Test locally: `npm start`
112
-
5. Commit with descriptive message: `git commit -m "Fix typo in environment setup guide"`
113
-
6. Push to your fork: `git push origin fix/update-documentation`
114
-
7. Create a Pull Request
115
-
116
-
#### For Large Changes
117
-
1.**First, create an issue** to discuss the proposed changes
118
-
2. Get feedback from maintainers
119
-
3. Follow the same process as small changes
120
-
4. Reference the issue in your PR description
107
+
1.**Discuss Proposed Changes**:
108
+
-**Create an Issue**: First, create a GitHub issue to propose your changes.
109
+
-**Contact a Developer Advocate**: Reach out to a Developer Advocate (e.g., in the Intersect Discord #developer-experience channel) to discuss the relevance and scope of the work.
110
+
111
+
2.**Agreement & Timeline**:
112
+
- Work should typically not begin until there is an agreement on the scope.
113
+
-**Timeline**: Timelines can be discussed, but **one week** is the standard duration for submitting a Pull Request (PR) after agreement.
114
+
115
+
3.**Implementation**:
116
+
- Fork the repository and create a feature branch.
117
+
- Make your changes and test locally.
118
+
119
+
4.**Submit Pull Request**:
120
+
- Create your PR and ensure it is linked to the issue.
0 commit comments