-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat(issues): create and list #693
Conversation
3b65c3b
to
f1dcac3
Compare
f1dcac3
to
c6f7a74
Compare
defbb83
to
3bff297
Compare
@kavitha186, we need unit tests to cover issue, list-issues, and list commands. Can you add those? I've started down this road with checkout.ts. Seems a bit bulky and in need of rework but thought I'd share how I'm thinking about adding coverage for commands. |
c6f7a74
to
dd8e026
Compare
@kavitha186, I've landed test coverage for all the existing commands. You should be good to go to do the same for the new commands introduced in this PR. |
f816316
to
2101b63
Compare
614b5e7
to
f328e68
Compare
@kavitha186, let’s add a screenshot of unit tests coverage. A recording demoing the functionality would be helpful too. |
|
2b5a342
to
2b6d751
Compare
2b6d751
to
36bd3e9
Compare
@kavitha186, I've created a v3 branch for the next major release of Shepherd. Let's use that branch instead of main for these changes. |
@aorinevo I rebased the branch from main previously. Is there anything required to be taken care from my end? |
Plan is to land #852 and then this PR, both on v3 branch along with other features and enhancements. Once landed, let's switch local use to v3 and let it bake for a certain period of time before we merge v3 down to main and release the next major version. What this means for this PR. Once CI failures are resolved and #852 is landed, we can merge this PR into v3 provided the changes comport with changes in #852. If not, it will likely require additional changes to this PR before landing. |
@kavitha186, when you get a chance, please resolve CI failures. |
054eb98
to
cb1681f
Compare
cb1681f
to
c0d4756
Compare
@aorinevo fixed the ci failures |
This PR is for the feature to post issues on the repositories with shepherd. if you are looking to post issues across multiple repositories, you can use the command "issue" to create, update , list posted issues and close issue
issue with the title, issue message, labels , state and state_reason provided in the migration scripts.
This enhancement feature is for the issue #87 and #590
Screenshots
Create Issue
Update Issue
Closing Issue
List Issues
Screencasts
Screen-2024-03-17-185925.mp4