An MSBuildTask that checks for known vulnerabilities. Inspired by OWASP SafeNuGet.
digitalcoyote/chocolatey-packages 3
Template repository for Chocolatey Automatic Package Updater Module
A user-friendly launcher for Bazel.
digitalcoyote/BuildTaskNuGetPackageTemplate 0
A template for creating a NuGet Package that runs an exec task at build
🧔🏽 Community fork of @meetfranz. Ferdi allows you to combine your favorite messaging services into one application
Git Extensions is a standalone UI tool for managing git repositories. It also integrates with Windows Explorer and Microsoft Visual Studio (2010/2012/2013/2015/2017).
C# Wrapper of HIDAPI from signal11, wrapper multiplatform, used for interfaction with generic HID Devices, USB or bluetooth
Jenkins CLI allows you manage your Jenkins as an easy way
Faster way to switch between clusters and namespaces in kubectl
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 4 days
push eventdigitalcoyote/chocolatey-packages
commit sha 4cd2ac50ecbde58e1112b11ab53ce6e90730b698
AU: 1 updated - bazelisk [skip ci]
push time in 4 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 4 days
push eventdigitalcoyote/chocolatey-packages
commit sha 7047198ed39ea02b79f0168ab7063fcac216e86a
AU: 1 updated - gitb [skip ci]
push time in 4 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 5 days
push eventdigitalcoyote/chocolatey-packages
commit sha 24b217fca33bca5dbdd09e234309ce16e7115426
AU: 1 updated - buffalo [skip ci]
push time in 5 days
push eventdigitalcoyote/gitextensions
commit sha 9ebdcd0cabe809b6a726d3b65e4a964d7b7f3606
Update layout Reduce margins and paddings * Update `FormClone` * Update `FormInit` * Update `FormStatus` * Update `FormCheckoutBranch` Relates to #6183 Fix Accept and Cancel buttons that get unset by adding buttons to the controls panel. Resolves #8521
commit sha ea9486dbfabe7160218ee7b8c84db1bdb082766f
update button mnemonic
commit sha 5628718a74f359bd6f090d5c19f333027fe92d7e
Merge pull request #8555 from BrianFreemanAtlanta/ResetFormButtonMnemonic
commit sha 0b5ecd2a5fe53fd5b76209e8aea7465a90fa2357
Merge pull request #8510 from RussKie/Update_layout
commit sha eee06f4c09c0acbbf3682698273a6e1a92ecd4e9
Dialogs layout alignment - `FormCreateBranch` Relates to #6183
commit sha 3b4492d1cc613fba8775ac06886ffc469b98bf3d
Merge pull request #8490 from RussKie/Dialogs_layout_alignment_FormCreateBranch
commit sha e073715c0d56352b6e4bb34e0b30b0a443e6537f
Fixes #8146 "Keyboard navigation : Enter Key should open a recent repository"
commit sha f5782e7c1018dffb97d950e1b1ad174fa5964fbb
Merge pull request #8537 from lhiginbotham/lhiginbotham/enter-to-open-repository Fixes #8146 "Keyboard navigation : Enter Key should open a recent repository"
commit sha e94b59aa68741b29f40201c107aec8a1bac10de4
FormEditor SaveCanges FormEditor Altered WriteAllText to bypass an issue with Hidden Files File.WriteAllBytes does not appear to have this issue.
push time in 7 days
push eventdigitalcoyote/gitextensions
commit sha 641ef2741002e3fb03f52097c800165c694a121f
Update GitUI/CommandsDialogs/FormEditor.cs Co-authored-by: Michael Seibt <36601201+mstv@users.noreply.github.com>
push time in 7 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 7 days
push eventdigitalcoyote/chocolatey-packages
commit sha 0cd4cce97085138971a72ef533d30e9d1035fca2
AU: 1 updated - smmdb-client [skip ci]
push time in 7 days
push eventdigitalcoyote/gitextensions
commit sha 5e2957d0a1f17850b8e418a5589255bce4c8968a
Update GitExtUtils/FileUtility.cs Co-authored-by: Michael Seibt <36601201+mstv@users.noreply.github.com>
push time in 8 days
push eventdigitalcoyote/gitextensions
commit sha a61ba6db086d6e3ba6c1e129fbc2777aaf02c491
Update GitExtUtils/FileUtility.cs Co-authored-by: Michael Seibt <36601201+mstv@users.noreply.github.com>
push time in 8 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 8 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 8 days
push eventdigitalcoyote/chocolatey-packages
commit sha e43a3b8f14d03b091c31cb6020cefed58f19e887
AU: 2 updated - bazelisk sidequest [skip ci]
push time in 8 days
issue commentadamhathcock/sharpcompress
Use GitHub actions for Build and Deploying to NuGet
I'm starting work, but before I forget, I was looking into it, and if you want to use Manual Release, I can set the workflow to trigger on Release in addition to PR/Push, but only publish to NuGet on Release.
Let me know what you feel comfortable with and I'll see what I can do to make it happen.
comment created time in 8 days
issue commentadamhathcock/sharpcompress
Use GitHub actions for Build and Deploying to NuGet
So far I've been doing things manually as changes have been few and very long inbetween. Not sure how I feel about transitioning to GitVersion and auto-magic releasing.
I set the release up so it would only make Draft Releases (creates the tag for the commit using the version that was generated. I can rip both of those out fairly easily.
Does doing gh release roll up PRs and/or issues into it? What kind of tagging am I going to have to switch to?
I can set the action to specifically ignore PR's and only look at the release branch (for testing I was using master). The tagging is the same that is used if you let GitHub create the tag by specifying a new tag name for a release. I set it up to use the version as the tag (I believe this should match the current convention).
If you wanted these to be there in case you ever decide to switch to it, I can comment it out as well and add a few extra lines to document what each piece is doing. I haven't fully switched to automatic releases yet myself.
comment created time in 8 days
push eventdigitalcoyote/gitextensions
commit sha 60f138dcab557014da35c40f9fcad716f2149da3
Detect when Azure DevOps token is invalid/expired and display an explicit error message. Better than the current behavior that is displaying nothing... It happens sometimes and is difficult to understand/detect when the token has expired (because maximum duration is 1 year)
commit sha 1d208d817b1c0df88218f924aac48c02637046cd
Being able to open Build Server Integration Settings Page from Unauthorized Access error TaskDialog popup.
commit sha 6b0242c93357f05c4088b108fbc45bed9e9b8f34
Fixes #8327
commit sha 4c3ca69c7d3ee7fbc501394e2146e4c54b8e92c4
Change FormBorderStyle from SizableToolWindow to SizableWindow
commit sha e37bf503b6e7d1a904223e5b3d603a260d21092a
Merge pull request #8541 from racecrew/bugfix/push_commit_does_clear_commit_message_when_confirm_box_appears Fixes #8327 push commit does clear commit message
commit sha a573768a5b2abebf0515fd95ec35291978f09219
Merge pull request #8543 from ivangrek/fix-6557
commit sha e0c31777d5c3732f44b030d9970861114170c866
Add 'Run script' command to branches pane context menu
commit sha 1d4c3c4befbbcd7d47f02b1ff7e3024846686b39
Merge pull request #8532 from pmiossec/azure_devops_invalid_token
commit sha 4b39a6ad17ca71f5a6f3d01a734318fd1c13e93e
FormPush multiple: force-with-lease if rejected
commit sha 7ce3785c867fe8316c527056dbcc6077103711ee
Merge pull request #8549 from gerhardol/feature/i8548-multiple-force-push FormPush multiple: force-with-lease if rejected
commit sha a1c3adc78a89fed5f0d6074454164ee42a5eba65
Merge pull request #8405 from ivangrek/fix-6307-4
commit sha 123f3c4cec7298457aeec23235ec44dc0fb34ab8
FormEditor SaveCanges FormEditor Altered WriteAllText to bypass an issue with Hidden Files File.WriteAllBytes does not appear to have this issue.
push time in 8 days
push eventdigitalcoyote/gitextensions
commit sha 60f138dcab557014da35c40f9fcad716f2149da3
Detect when Azure DevOps token is invalid/expired and display an explicit error message. Better than the current behavior that is displaying nothing... It happens sometimes and is difficult to understand/detect when the token has expired (because maximum duration is 1 year)
commit sha 1d208d817b1c0df88218f924aac48c02637046cd
Being able to open Build Server Integration Settings Page from Unauthorized Access error TaskDialog popup.
commit sha 6b0242c93357f05c4088b108fbc45bed9e9b8f34
Fixes #8327
commit sha 4c3ca69c7d3ee7fbc501394e2146e4c54b8e92c4
Change FormBorderStyle from SizableToolWindow to SizableWindow
commit sha e37bf503b6e7d1a904223e5b3d603a260d21092a
Merge pull request #8541 from racecrew/bugfix/push_commit_does_clear_commit_message_when_confirm_box_appears Fixes #8327 push commit does clear commit message
commit sha a573768a5b2abebf0515fd95ec35291978f09219
Merge pull request #8543 from ivangrek/fix-6557
commit sha e0c31777d5c3732f44b030d9970861114170c866
Add 'Run script' command to branches pane context menu
commit sha 1d4c3c4befbbcd7d47f02b1ff7e3024846686b39
Merge pull request #8532 from pmiossec/azure_devops_invalid_token
commit sha 4b39a6ad17ca71f5a6f3d01a734318fd1c13e93e
FormPush multiple: force-with-lease if rejected
commit sha 7ce3785c867fe8316c527056dbcc6077103711ee
Merge pull request #8549 from gerhardol/feature/i8548-multiple-force-push FormPush multiple: force-with-lease if rejected
commit sha a1c3adc78a89fed5f0d6074454164ee42a5eba65
Merge pull request #8405 from ivangrek/fix-6307-4
commit sha 8318e22430c2b4dd1ceef063d1dffe736b6284e0
Parallelized Repo Validity Checks This should prevent "hanging" during startup as described in #8337
push time in 8 days
pull request commentgetferdi/ferdi
Add Chocolatey install instructions for Windows
I noticed that, it can be downloaded right now by specifying the version (bypasses moderation). But I believe it should be reviewed fairly soon as most of the other submissions I made in that time range have been reviewed now.
comment created time in 9 days
pull request commentgitextensions/gitextensions
Parallelized Repo Validity Checks during Startup
So the PR is making it slower? I'm confused, sorry.
That was done in a Windows VM with only 2 logical processors (1 core) on a Linux Dev Machine. I booted over to my Windows install, updated for several hours, and tested again. In addition, I did tests with repos on Shares that are no longer connected. The additional plumbing that its doing behind the scenes to add in those extra threads makes it slower by ~10-20ms when everything is valid. But, it prevents hanging up (or at least shortens the hang) when repos on network shares are missing.
30 Invalid Network Shares
Old Code on a single core: ~ 30 seconds PR Code on a single core: ~15 seconds
Old Code on 8-core: ~30 seconds PR Code on 8-core: ~2.5 seconds
It and it appears that it takes ~ 2-2.5 seconds for it to time out when looking for a network share.
30 Repos not on network shares (valid or not seems not to matter much)
Old Code on single core: 20-30ms PR Code on single core: 30-40ms
Old Code on 8-core: 20-30ms PR Code on 8-core: 30-40ms
comment created time in 10 days
issue commentbazelbuild/bazelisk
Request: Publish Chocolatey Package
It's approved.
When they approved it, it immediately queued up the next version and I didn't notice it had been approved.
On Sat, Oct 17, 2020, 12:44 PM UebelAndre notifications@github.com wrote:
Any updates on the published package? Will it work by simply running choco install bazelisk if the security exception has been fixed?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bazelbuild/bazelisk/issues/161#issuecomment-711055613, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEAWF7O6KHNX26JFDR36CBDSLHJYBANCNFSM4Q4S7LXA .
comment created time in 10 days
issue commentauthpass/authpass
Windows: Package and publish through Chocolatey
I have several trusted packages, so it should happen eventually. Normally it requires the software author to be the one who creates/maintains the software. They partially need to verify that the update process is reliable.
On Sat, Oct 17, 2020, 10:54 AM Herbert Poul notifications@github.com wrote:
@digitalcoyote https://github.com/digitalcoyote ok cool thanks :-) is there something we can/should do to get "trusted" or is it just a matter of having enough accepted versions?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/authpass/authpass/issues/117#issuecomment-711034000, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEAWF7N7JOMA26PMNHNIU63SLG42LANCNFSM4PH6S7GA .
comment created time in 10 days
issue commentauthpass/authpass
Windows: Package and publish through Chocolatey
https://chocolatey.org/packages/authpass#versionhistory shows that it's been submitted. Unfortunately, until the package is "trusted" it has to go through review with each version.
comment created time in 10 days
issue commentauthpass/authpass
Windows: Package and publish through Chocolatey
It runs ~about every 12 hours to look for updates to packages. I went ahead and triggered an early check, so it should be updating now.
comment created time in 10 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 10 days
push eventdigitalcoyote/chocolatey-packages
commit sha 04a43d96629da60107db3da9b1ab2e0fc01c0f49
AU: 1 updated - authpass [skip ci]
push time in 10 days
PR opened adamhathcock/sharpcompress
In response to #506
Changes Not Directly Related to Automated Release/Push
- Updated Checkout Action
- seems there have been many improvements since v1
- Removed dotnet-setup
- unnecessary as all the images used have the specified dotnet sdk pre-installed
GitVersion changes
string version = args.Length > 0 ? args[0] : ""; and RunTargetsAndExit(args.Skip(1).ToArray()); kinda bother me, but I wasn't sure how you would want to handle it, so I did a quick and dirty that allowed automation to run, but does require you to give it a version when specifying a target. I could just write it to a file and pull it in if the file exists if you want.
GitVersion is fairly configurable, and you can manually push/create tags to change the major/minor revisions without configuring anything.
Gihtub Releases
This is dependant on a github token being created (and stored as a secret with the name SharpCompress_Token. It needs the repo and read:org scopes (https://github.com/settings/tokens). If you add it as a secret for this repo, even if an action printed it to the logs, it should be sanitized before it was written.
I have it set to save them as drafts with the nuget and symbol package attached. This should allow you to fill in wahtever release notes you like before publishing. This can be configured.
NuGet Releases
Similar to GitHub Releases, you need a secret named SharpCompress_NuGet_Token that can be retrieved from your NuGet account. I have it overriding the versions in the file on build, so they will be automatic thanks to GitVersion.
Let me know if there are Any changes needed or things that you may need help setting up or working with (I'll do what I can without compromising the security of the repo).
pr created time in 10 days
push eventdigitalcoyote/sharpcompress
commit sha 47d71313325cddc133f6bda681c5276ade74a08c
Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha e16aaeb8f891520a52769830b86d268c9c899ad6
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 56cef8ce5919957e25a3209b3bdaecb4162b71cc
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/NuGetDefense
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha c8f1a3f3ea4c517b117156351aaf650bd3d8fb2d
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 76dbbdab830a7c2300dee04544425bc4ecf58d61
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha a4141189010f4d2bccccc7c057b040272c8d9749
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha b34836b9f7207e608f30205fab895b4ded3d59bb
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha ee1060bfa6412c7a104515473e8d77d63f515067
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha bb77beca4cbf89ab55d5ef9a84bea45208a3322b
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 54f4b2752a6e0b2b36dd35452f68c652e9afd655
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 584cf3ea34001cba4efa32c002d8ea97d6012af9
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha d9ac4cac8790470a9875eeb963a2d841b34b89d0
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha bdae98f280c457b6916487ab736c996d4f5d14f4
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 948175f6c3761363f37f8ad0d77c1d18307a3555
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 8d04397d4275ce3053e1aca2e678cdbe9a99a1f2
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha e636d28b23fa9f85d682f57559ffc304bd489a21
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 2b3e0114236caa7bb7a37f668139533a823f2fd8
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha aec448137d86ae4c3db123833066104bce10b479
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha f2c2362e88f11015907b58cd59508f443db21f9e
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 3d24ae626d6e7c08182884a4f9464dd3d12606a3
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha b456af5f7a09ec295bd14caa546dec99c870912c
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 8bd10cbd588ab3a29e00ca48d2bef868e8157331
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 468954dbf7fd67d4962d37bbabbe46c4f30dc006
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/NuGetDefense
commit sha f75d32981a8a8d18e3bc14232294951398d58618
1.0.13.1 changes Mainly Just Added the Icon
commit sha e9965ca48a4b4a0d20d755dec57ce37f89fc7540
Updating GitHub Actions
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 1cb03aba6cda8c8903b439d23761caa91c9b709d
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 7737b3a431ec0e8cedb8b8b0745afe796b20b79f
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 18d0e6e5785e2294b96afaf8824a9288398feeb6
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha b0938cc7d55a32d8c036c56dad74e9dd167694f0
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 8a5e28af50a8c47d02256c715805ad6b81c4aa7c
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha ede4e2649299c253dd7671a824237e2b57e3ec63
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 89799b392e93bc3d952974599cd7b1b1ecc1da22
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 892a6d54872b1b34be8522ebb832d2298f663bc7
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha cc848617aeb1bb1d44f94a6c0145a12eb555ce09
WIP: Automated Publish to NuGet
push time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha bee01e7045f82e7673509637451a3da313909a40
WIP: Automated Publish to NuGet
push time in 11 days
issue commentadamhathcock/sharpcompress
Use GitHub actions for Build and Deploying to NuGet
I finally got around to starting on this.
- Do you intend to version releases manually?
- or would you like to use something like GitVersion?
- Also, with the GitHub CLI, it could create the actual GitHub release as part of the action
I'm currently working under the assumption of using gitversion and passing the version as an argument to the build script (so it can be ignored and allow the project to be built if gitversion is not installed). I hope to have it running without the actual nuget publish later tonight.
comment created time in 11 days
push eventdigitalcoyote/sharpcompress
commit sha 732fae4056415636ef5ca18342608587a5ba2c55
Removing DotnetSetup All supported versions of the .Net SDK's are included by default on each OS image.
push time in 11 days
fork digitalcoyote/sharpcompress
SharpCompress is a fully managed C# library to deal with many compression types and formats.
fork in 11 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 11 days
push eventdigitalcoyote/chocolatey-packages
commit sha 1659e34ed0eb31ca2e4cd28b7f595f612dadbf82
AU: 1 updated - bazelisk [skip ci]
push time in 11 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 13 days
push eventdigitalcoyote/chocolatey-packages
commit sha 033713ca672e92b8cd38fde9ae835769d0a0b375
AU: 1 updated - sidequest [skip ci]
push time in 13 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 13 days
push eventdigitalcoyote/chocolatey-packages
commit sha 6f9656dc03abd5713bd19b46553bafdc49ce030c
AU: 1 updated - sidequest [skip ci]
push time in 13 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 13 days
push eventdigitalcoyote/chocolatey-packages
commit sha 0a3d33be1c1004218b49fa28ac6df1bda736da31
AU: 1 updated - smmdb-client [skip ci]
push time in 13 days
pull request commentgitextensions/gitextensions
Parallelized Repo Validity Checks during Startup
I went ahead and checked out the .Net 5 branch and wrote up an async enumerable version of this change. was much slower due to that requiring BindRepositories to be async. The extra plumbing required to make sure the listview items were on the UI Thread had a bit of a negative impact. I'm going to start setting up repos for the test I mentioned above. Will probably be tomorrow or the next day after work before I can sit down and take some measurements.
comment created time in 14 days
push eventdigitalcoyote/gitextensions
commit sha e2c318bb55412dc494c530a3df9b2fd4c52f646d
Hide filtered out refs Indicate branches and tags in the left panel that are currently filtered out and not visible in the revision grid. * The hidden refs are greyed out and their icon is changed to "closed eye". * Each node in the tree now has a new property `IsVisible` that can be used as a conditional flag when implementing necessary logic. * Apply the same style to branches in the Recent branches toolstrip dropdown. Detection of whether a given ref is visible or not is done by checking the revision grid, which is currently the source of truth. Whenever the revision grid is refreshed, it raises an event that causes the left panel to update its state, and show or hide nodes.
commit sha 92e7f81fb6a10851967768b34c7da522d6fa3b15
FileViewer: ViewMode to track what is currently displayed Refactor to handle the different "modes" like diff/text in a simpler way Add a FixedDiff mode to display patched with fixed comments that will not be changed by i.e. whitespace changes. Refresh when changing highlighting. * ViewPullRequestsForm (GitHub PR) * FormViewPatch * FormVerify
commit sha 349910ce33587b6f4fef86aa5beed0de26e363d0
Longer GPG key input box (8 -> 16)
commit sha 8455de97db9b94b71ceedfd870994c1256f89451
Merge pull request #8414 from RussKie/Filter_out_hidden_branches
commit sha 730667814ad89e199efafaab536f95c77a54b744
Merge pull request #8509 from oriash93/oriash93/longer_gpg_support Longer GPG key input box (8 chars -> 16 chars)
commit sha ee79afc2a19c0fe5c9f953b16cea5ce8e82a7560
Don't refresh revision grid invoking toolstrip actions Appears to be a regression from #8485 which caused the revision grid to be refreshed whenever an action was raised via the toolstrip, e.g. invoking fetch would refresh the grid before the fetch operation was performed, as well as after. Somehow the toolstrip would pass focus to all its items, that included the Branch Filter which in turn would cause the refresh. Update the logic to force the grid refresh only when the filter is being changed and applied. What's worse, multiple refreshes could overlap each other due to peculiar behaviour of the toolstrip, which keeps on passing focus back to its items, and with that invoke `FilterBranchHelper.toolStripBranches_Leave()`. There was also another strange behaviour that could lead to a blank revision grid - if a user typed a filter but hasn't applied it, and then invoked another action via the toolstrip (e.g. fetch) - the revision grid would refresh first after the fetch, and then another refresh operation would be in flight that attempted to apply the pending filter. Remove the method and in essence change the user behaviour - now users have to hit ENTER to apply a filter rather than leave the filter textbox. And move the latch in `ForceRefreshRevisions()` a little higher, to reduce risks of race refreshes. Also do not refresh the grid when fetching the status from the superproject if the status hasn't changed.
commit sha 4f7901329258f7a93533bdbfb14944ed9b99f322
Merge pull request #8496 from gerhardol/feature/fileviewer-viewmode FileViewer: ViewMode to track what is currently displayed
commit sha b1ba97457f752d0f5191617736a9a34774c3ba7d
Push multiple: Set default push to false
commit sha 37dbf4bf4749b886176185edaf6e4cf500949ace
Merge pull request #8511 from RussKie/Dont_refresh_twice Don't refresh revision grid invoking toolstrip actions
commit sha eb120cd8201dae89493f5090d51fef2f5f1a5108
Added myself as a contributor.
commit sha a6baf309e1e0cd4f2520005a45f7e9e6396980d6
Merge pull request #8518 from GintasS/update-contributors Added myself as a contributor.
commit sha e1b3b0109dd62a12e0c3dbc15a30750d487d4d8f
Merge pull request #8515 from gerhardol/feature/multiple-push-default-false Push multiple: Set default push to false
commit sha d8d2268604b9e6544d66b4e4971ed40597561e45
FormPush: Add context menu to easily manage multiple push selection * Add an option to unselect all * Add an option to select all * Add an option to select only the ones already tracked (default state)
commit sha fc459d4c49391c37f9ac55342fb4c9ad580f3799
Apply action to all selected files in solve merge conflict - Replace a custom dialog ResolveFilesConflict by a TaskDialog - Show a check box "apply to all files" if there are more then one conflicted files - There could be different types of changes by multiple selected files, e.g. deleted locally and modified remotely and vice versa. In this case the "Merge Dialog" will recognize it and process the same types of files changes at once and prompt a dialog only if type of changes will be different - Some parts of the code are refactored - Rework text messages in the Task Dialog - Refactor code - Change wordings in dialog text - Minor code changes - Rename variables and remove unnecessary comments
commit sha 2664f26ddf6a5a91e0bbbdf82c5eba2500ed34bb
Use SelectedNode property to track target for context menu
commit sha 19f3a34e862fe43bc55c85672146147afe73e766
Merge pull request #8501 from racecrew/feature/ApplyActionToAllSelectedFilesInSolveMergeConflict
commit sha 545d6b23b968e95b5b7fd5359d82d3256cd3661c
Merge pull request #8520 from pmiossec/form_push_manage_selection FormPush: Add context menu to easily manage multiple push selection
commit sha 5f11bf2119cddb1763f0c2934c0eae2cd4f6de70
Merge pull request #8528 from mdonatas/left-pane-context-menu-fix
commit sha cba534d6962c14f3efe50e8385d103e95f01d823
RevisionGrid: Prevent inopportune crash when right clicking in the grid Fixes #8475
commit sha fcd7957f246222bd54c0412d0d76963277855208
Merge pull request #8534 from pmiossec/revision_grid_prevent_crash RevisionGrid: Prevent inopportune crash
push time in 14 days
push eventdigitalcoyote/gitextensions
commit sha b17be1e7647ec99e9c599d14e478b754260e4aee
update RemoveFiles to use GetBatchOutput and add unit tests.
commit sha 88b28174d651e8a9c4b7187f13a605b07e31bd0d
Agree to The Developer Certificate of Origin. (#8536)
commit sha 43557461def26bbcfe7ef982c04cf6a7559c38a1
Merge pull request #8527 from BrianFreemanAtlanta/RemoveFilesUpdateNameTooLong updated removeFiles to use GetBatchOutput and added unit tests
commit sha 42a6bc7dec7efd69516321c030e20bd83e992c09
Submodules window now keeps the splitter position Added myself as contributor
commit sha d25b2b8e36b84f626185db47cc2ad2dcd09c8d05
Merge pull request #8525 from JurjenBiewenga/feature/save-splitter-submodules Submodules window now keeps the splitter position
commit sha 19aef85b2d1683d51eeaf1b9f9dc1d5d43e83c5b
Add ability to Copy to Clipboard, similar to commit context menu from left panel
commit sha 75c7aaed8703dc33dcd96e48733cf998340d324c
Merge pull request #6339 from ivangrek/fix-6304
commit sha 5fdb8f4d8849c2317438ebd0c3c94e90fc5aa25f
RevDiff: Remove irrelevant context menu items for CombinedDiff Also for status items (Git Errors) Added a few tests for the missing behavior
commit sha b1697bb53a39f646d0e4a157c35341965758fe46
Ensure focus on cancel button by changing tabIndex
commit sha ef43da287dd1d3894d5896a720837a48979eb2fa
FileStatusList: Refactor FileStatusDiffCalculator to own file Diff first and last if many selected in grid Instead of first and second Refactoring: use private class instead of tuples Refactoring: Early return in SetDiffs() Assume 4 selections are two ranges When selecting 3 or 4 commits show common/unique diff if common base (when first/last is in different branches) If no common base, show multi diff (as is currently) For 4 assume that selection is done in ranges, i.e. baseA..headA and baseB..headB where A and B are in separate branches. Therefore use the second selected commit as "first" This is a preparation for comparing ranges
commit sha c1a0d7df68793496959e06f1a7b17d6970006ea7
Show range-diff for commits in separate branches Git range-diff output for two related commits Show a summary with how to run the command from a Git terminal if the "symmetric difference" between the commits exceeds 100
commit sha f1befaefae86764961c37a306ee0f2e21ac33cc9
VisualStudio designer stuffs
commit sha fbfaea1abf910901f235334a674774732d8444eb
Being able to open Application and User theme folders
commit sha fcdf2a8777e8755af3fcaa92c5a18b912bb7f729
Use a table layout
commit sha f8f0265f0e5f37dc9bf6a918dbc04490881cde54
BackgroundFetch: add a warning message for when using the "git push --force-with-lease" feature
commit sha daa7ce1929d6e6417ed8e242148d35b6fddcdd58
Merge pull request #8502 from pmiossec/open_themes_folders Add a button to be able to open Application and User theme folders
commit sha 99df5a6f7ea003c1e8fbc3b2c8b598d40735f705
Merge pull request #8533 from pmiossec/warning_bckg_fetch_force_with_lease
commit sha 298380268b488fe4f799a62a799e7c07bb66c8e8
Merge pull request #8524 from BrianFreemanAtlanta/ResetFormButtonFocus
commit sha 35cf98528898c01dba92ce23712197028298a7e6
Merge pull request #8471 from gerhardol/feature/i8448-range-diff
commit sha 523728c9f56bff5815619989384d2e9795501d18
FormEditor SaveCanges FormEditor Altered WriteAllText to bypass an issue with Hidden Files File.WriteAllBytes does not appear to have this issue.
push time in 14 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 14 days
push eventdigitalcoyote/chocolatey-packages
commit sha 0658ee9ae257214cb6354d0b791cc3bdfd36f2ee
AU: 1 updated - smmdb-client [skip ci]
push time in 14 days
created tagdigitalcoyote/chocolatey-packages
Template repository for Chocolatey Automatic Package Updater Module
created time in 15 days
push eventdigitalcoyote/chocolatey-packages
commit sha a46b2f2c462db193dbdbc9e7c2c267feb5b62720
AU: 1 updated - jcli [skip ci]
push time in 15 days
push eventdigitalcoyote/chocolatey-packages
commit sha 1fc5183879a536d05c2ba0d6478498894d6eae46
Updating kubens
commit sha 8f48a8ba1d9f089e870cda3ccf6b37e677d85177
Adding jcli back
push time in 15 days
startednayafia/contributing-template
started time in 15 days