Completion Predictor v0.1.1<\/h2>\n
If you are unfamiliar with the Completion Predictor, this is a plugin in predictor that we released\nlast year that provides tab completion to help give prediction results. This means it can work for\nhelping fill out parameters of cmdlets and properties and methods of objects. The Version 0.1.1\nrelease contains some experience improvements and some new completion capabilities.<\/p>\n
Installing Completion Predictor v0.1.1<\/h2>\n
First and foremost, how can you get this predictor? The release is available from the\nPowerShell Gallery<\/a>.<\/p>\n Use the following command to install CompletionPredictor<\/strong> using PowerShellGet<\/strong> v2.x:<\/p>\n If you are using PowerShellGet<\/strong> v3, you can use the following command:<\/p>\n Using tab completion we’re able to give predictions on the next folders you may want to navigate to\nwith Another argument completion improvement was with Completion Predictor is able to look at remote and local branches available to accelerate your flow\nwhen using <\/p>\n Similarly, to the merge behavior, the completion predictor is now able to give predictions on what\nbranch you may want to use when checking out or deleting branches. This only works with the\nsubcommands As I mentioned, we added these improvements to help with our specific This isn’t a blog post about how to best use You can find the rest of the changes in this release in the changelog<\/a> on the release page. We\nlove getting feedback on these predictors we make! The entire source code for this predictor is\navailable on GitHub<\/a> and can be a great starting point for making your own predictor! Please\nfeel free to open issues or PRs on the GitHub page for improvements that may work for you and\nothers! Enjoy!<\/p>\n Steven Bucher and Dongbo Wang<\/p>\n Completion Predictor and PSReadLine Maintainers<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" We released a new version of the CompletionPredictor! This blog post highlights some of the new functionalities of it.<\/p>\n","protected":false},"author":98569,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[3188,3168],"class_list":["post-19963","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell","tag-predictors","tag-psreadline"],"acf":[],"blog_post_summary":" We released a new version of the CompletionPredictor! This blog post highlights some of the new functionalities of it.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/19963","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/98569"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=19963"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/19963\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=19963"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=19963"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=19963"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Install-Module -Name CompletionPredictor<\/code><\/pre>\nInstall-PSResource -Name CompletionPredictor<\/code><\/pre>\nArgument Completion Improvements<\/h2>\n
cd and dir<\/h3>\n
cd<\/code> or view the contents of with dir<\/code>.<\/p>\n![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/powershell\/wp-content\/uploads\/sites\/30\/2023\/05\/cddirCompletionPredictor.gif\")
<\/a><\/p>\ngit<\/h3>\n
git<\/code>. These are improvements that we’ve found\nworks best for our workflow but may help with your git<\/code> workflow as well!<\/p>\nMerging branches<\/h4>\n
git merge<\/code>. Here is an example of it working.<\/p>\n![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/powershell\/wp-content\/uploads\/sites\/30\/2023\/05\/git-merge.gif\")
<\/a><\/p>\nChecking out and deleting branches<\/h4>\n
git checkout<\/code> and git branch -D<\/code>. The predictor intentionally doesn’t include the\ncurrent branch you are in when giving results.<\/p>\n![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/powershell\/wp-content\/uploads\/sites\/30\/2023\/05\/gitcheckoutbranch.gif\")
<\/a><\/p>\ngit<\/code> workflows. Typically, the\nrough flow we’ve is the following:<\/p>\n\n
git fetch --all -p<\/code> -> to get the latest changes in that repo<\/li>\ngit merge<\/code> -> sync the default branch<\/li>\ngit branch -D<\/code> -> delete the old working branches that were already removed from the remote side<\/li>\ngit checkout<\/code> -> checkout a new branch to work in<\/li>\ngit push<\/code> -> push the new branch to remote to then create a PR<\/li>\n<\/ul>\ngit<\/code>, so please refer to other online resources to\nlearn git<\/code>. This is just the workflow we like to use that helped us create the git<\/code> improvements\nto the Completion Predictor.<\/p>\nFeedback<\/h2>\n