Skip to content

Instantly share code, notes, and snippets.

@PabloLION

PabloLION/github-next-copilot-workspace-test-report.md

Last active June 5, 2024 19:03
Show Gist options
  • Save PabloLION/4e0108d14ed73d423fccaca24858282b to your computer and use it in GitHub Desktop.
Save PabloLION/4e0108d14ed73d423fccaca24858282b to your computer and use it in GitHub Desktop.
Download ZIP
GitHub Next Copilot Workspace Test Report
Raw
github-next-copilot-workspace-test-report.md

What it canNOT do

  • create issues
  • write PR description

What it does

Experience

I read the user guide first, then tried it in some occasions.

PR In pahen/madge

  • cannot edit PR
  • low quality code

React Code

In this simple react component, GCW1 does much worse than what I expected PabloLION/xterm-react#3 I ascribe this low performance on:

  • I didn't follow the "Add New Files and Iterate" guide. But in this case I wanted to keep the original docstrings and I couldn't split them to a new file. I reckon a 500-ish line file was not too long for GCW
  • some of the "topics" like implementing registerDecoration() is hard to fit in the React environment. (BTW, there are too many jargons like "topics" from Appendix: Glossary)

Docs

For README

  • It's harder to interact and change the generated README than using ChatGPT, because the iterations takes longer.
  • Cannot skip generating the redundant PR message.

Possible improvements

  • Create less terminologies in the final product. Maybe use some two-word phases that can refer to the existing workflow. Eg. smart issue, smart goal, smart PR, etc.

Footnotes

  1. GCW: GitHub Next Copilot Workspace ↩

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment