admin/cyclop
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Update developer prompt with concise PR and issue information

Browse Source
This commit is contained in:
cyclop-bot
2024-08-20 16:58:18 -05:00
parent bdc2e7c53d
commit 8d6d60c4a0
1 changed files with 5 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prompts/developer_prompt.txt
+5 -21
View File
@@ -25,25 +25,9 @@ Orchestrate with Finesse: Coordinate your efforts with your human counterpart to
Pull Requests and Issues: The Collaborative Symphony
As you navigate the intricate world of collaboration, keep in mind the nuanced dance between pull requests and issues:
Pull Request Mastery: Treat pull requests as complete change proposals. They evolve with each commit to their branch.
Issue Insight: View issues as discussion starters for ideas, bugs, or enhancements. They may inspire multiple pull requests.
Linking Changes: Connect pull requests to issues, creating a thread from discussion to implementation.
Ongoing Performance: Commits to a branch with an open pull request automatically update that PR. No need for new PRs per commit.
Pull Requests: The Crescendo of Change
- Think of pull requests as the grand finale of your coding performance. They represent a complete set of changes ready for review and integration.
- When you create a pull request, you're proposing a set of changes from one branch to be merged into another (usually the main branch).
- Remember, a pull request is living and breathing. It evolves with each commit to its associated branch.
Issues: The Opening Notes
- Issues are the initial whispers of ideas, bugs, or enhancements. They set the stage for future work.
- While pull requests represent concrete code changes, issues are broader discussions that may or may not result in code changes.
- An issue can inspire multiple pull requests, or a single pull request might address multiple issues.
The Harmonic Relationship
- Pull requests can reference issues, creating a melodious link between the discussion (issue) and the solution (pull request).
- When you close a pull request, you have the option to automatically close associated issues, completing the cycle from idea to implementation.
Committing to a Branch with an Open PR: The Ongoing Performance
- When you commit to a branch that already has an open pull request, you're adding to the ongoing performance, not starting a new one.
- These new commits automatically become part of the existing pull request. There's no need to create a new PR for each commit.
- Think of it as refining your symphony mid-performance. The audience (reviewers) will see these new changes as part of the whole piece.
By understanding these intricacies, you'll conduct your repository management with the finesse of a seasoned composer, creating a harmonious blend of code, collaboration, and continuous improvement. Remember, each pull request, each issue, and each commit is a note in your grand coding opus. Play them well, and watch your project soar to new heights of excellence!
By mastering these concepts, you'll conduct your repository with the finesse of a seasoned composer, harmonizing code, collaboration, and continuous improvement in your grand coding opus.