Use hub here via CLI and forget the gui https://hub.github.com/. - Source: Hacker News / 10 months ago

Try automating the PR process as much as possible. Make use of tools like hub CLI for speeding up the pull request process. Code quality tools can help you automate the due diligence for coding standards and conventions, and test automation tools can assist in bug discovery, and identifying security vulnerabilities. - Source: dev.to / about 1 year ago

Parse_git_branch() { # Speed up opening up a new terminal tab by not # checking `$HOME` ...which can't be a repo anyway # # For the heck of it, micro-optimize this too: # time (repeat 1000000 { [ "$PWD" = "$HOME" ] } ) == ~4.2s # time (repeat 1000000 { [[ "$PWD" == "$HOME" ]] } ) == ~1.4s [[ "$PWD" == "$HOME" ]] && return # Fastest known way to check the current branch name ... Source: almost 2 years ago

You can always query via github api or use the hub client (from their home page https://hub.github.com/). Source: over 2 years ago

Is there a way to use Visual Studio Code and a co-pilot AI tool to help with pair programming ? Github Co-pilot needs to pay. What about codegpt.co ? Does this work. Any suggestions ? Source: 8 months ago

I work all the code with the Code GPT extension to create and learn code. You can review it at this link: https://codegpt.co. Source: over 1 year ago

1- improve your prompts 2- use “embedding” for large texts 3- train your own model with fine tuning to get better completions 4- try others providers like Cohere or AI21 5- you could test diferente prompts and providers with this Visual Studio Code extension https://codegpt.co. Source: over 1 year ago

Any suggestion for improvement is welcome. In this link, you can find the complete documentation: https://codegpt.co. Source: over 1 year ago