-
Notifications
You must be signed in to change notification settings - Fork 0
Comparing changes
Open a pull request
base repository: fredatgithub/copilot-cli
base: 4b16981
head repository: github/copilot-cli
compare: 65677f8
- 10 commits
- 2 files changed
- 5 contributors
Commits on Mar 23, 2026
-
Configuration menu - View commit details
-
Copy full SHA for ab1336d - Browse repository at this point
Copy the full SHA ab1336dView commit details
Commits on Mar 26, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 2a03ddf - Browse repository at this point
Copy the full SHA 2a03ddfView commit details -
Sort git tags when determining prerelease version
Tags are sorted lexicographically by default, not by version, so for example right now `git ls-remote` for this repo shows: ``` $ git ls-remote --tags \ https://github.com/github/copilot-cli \ | tail -3 | awk -F/ '{print$NF}' v1.0.8 v1.0.8-0 v1.0.9 ``` With the sort option, it shows the correct latest prerelease tags: ``` $ git ls-remote --tags --sort "version:refname" \ https://github.com/github/copilot-cli \ | tail -3 | awk -F/ '{print$NF}' v1.0.12-0 v1.0.12-1 v1.0.12-2 ``` This option for git ls-remote was added in git version 2.18.0 in June 2018: https://github.com/git/git/blob/v2.18.0/Documentation/RelNotes/2.18.0.txt#L69-L70
Configuration menu - View commit details
-
Copy full SHA for 3d2b5b5 - Browse repository at this point
Copy the full SHA 3d2b5b5View commit details -
Merge pull request github#2331 from gulducat/patch-1
Sort git tags when determining prerelease version
Configuration menu - View commit details
-
Copy full SHA for b175fd8 - Browse repository at this point
Copy the full SHA b175fd8View commit details
Commits on Mar 29, 2026
-
install: add fish shell support for PATH configuration
Fish shell users currently fall into the catch-all case, which writes POSIX export syntax to ~/.profile. Fish does not source ~/.profile and does not use export PATH="...:$PATH" syntax, so the PATH addition silently does nothing. Add a fish case that targets the idiomatic conf.d directory and uses fish_add_path, matching how the script already handles zsh and bash with their respective profile files and syntax. Extract the PATH command into a variable to avoid duplicating the shell-specific logic across the interactive prompt, non-interactive hint, and get-started instructions.
Configuration menu - View commit details
-
Copy full SHA for 07af0bc - Browse repository at this point
Copy the full SHA 07af0bcView commit details -
install: use EXIT trap for temp directory cleanup
Replace scattered rm -rf calls with a single EXIT trap to ensure the temp directory is always cleaned up on exit. Previously, failures in curl/wget download, tar extraction, chmod, or mkdir left temp files behind because set -e would exit before reaching manual cleanup calls. The trap fires on any exit (success or failure), so it covers all paths with one line while removing five redundant cleanup calls.
Configuration menu - View commit details
-
Copy full SHA for 177b637 - Browse repository at this point
Copy the full SHA 177b637View commit details -
Merge pull request github#2380 from marcelsafin/fix/install-trap-cleanup
install: use EXIT trap for temp directory cleanup
Configuration menu - View commit details
-
Copy full SHA for a503500 - Browse repository at this point
Copy the full SHA a503500View commit details -
Merge pull request github#2381 from marcelsafin/fix/install-fish-shel…
…l-path install: add fish shell support for PATH configuration
Configuration menu - View commit details
-
Copy full SHA for 9c1a0ae - Browse repository at this point
Copy the full SHA 9c1a0aeView commit details
Commits on Mar 30, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 2ecd9e1 - Browse repository at this point
Copy the full SHA 2ecd9e1View commit details
Commits on Mar 31, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 65677f8 - Browse repository at this point
Copy the full SHA 65677f8View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 4b16981...65677f8