-
Notifications
You must be signed in to change notification settings - Fork 5
949: Added workflow.md file #904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| # Feature Workflow | ||
|
|
||
| Use this flow when handling a feature from assignment through merge and handoff. | ||
|
|
||
| ## Workflow | ||
|
|
||
| 1. Read the task description in Notion and understand the requested change/feature. | ||
| 2. Set the Notion ticket status to `In Progress`. | ||
| 3. Pull the latest `main` branch. | ||
| 4. Create a local branch named exactly the Notion ticket ID. | ||
| 5. Make every commit message start with `<ticket-id>: `. | ||
| 6. Open a pull request when the change/feature is completed. | ||
| 7. Set the Notion ticket status to `Pending PR`. | ||
|
Arshadul-Monir marked this conversation as resolved.
|
||
| 8. Add a clear PR description. | ||
| 9. Add a screenshot from the development environment (if available). | ||
| 10. Deploy the feature to staging (type /deploy in the PR comments). | ||
|
Arshadul-Monir marked this conversation as resolved.
|
||
| 11. Add a screenshot from the staging environment (if available). | ||
| 12. Ensure all PR checklist items are completed. | ||
| 13. Resolve any Copilot suggestions. | ||
| 14. Ping a reviewer on discord. | ||
| 15. Resolve reviewer comments. | ||
| 16. Rebase and merge the branch into `main`. | ||
| 17. Set the Notion ticket status to `Done`. | ||
|
|
||
| ## Notes | ||
|
|
||
| - Keep the branch name and commit prefix aligned with the same ticket ID. | ||
| - If screenshots are not available, note that in the PR description. | ||
| - Try to squash commits when possible. | ||
| - Example: If you have a commit like "checkstyle fix", squash it into the most relevant feature commit. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.