Граф коммитов

4 Коммитов

Автор SHA1 Сообщение Дата
Billy O'Neal 141061ef9b
Sign posh-vcpkg.psd1 (#1432)
Just like posh-vcpkg.psm1
2024-06-21 15:54:03 -07:00
Javier Matos Denizac 296a34e6cd
Add "verify-messages" target (#1372)
* should be forward slashes

* add script to check for unused messages

* add messages check to pr workflow

* error if unused messages

* dont print every message every time

* remove bogus comment

* remove bogus comment

* remove bogus comment (again)

* Remove timer; add word boundry to regex;merge format and very messages job in pr.yaml

* Use JSON files instead of REGEX to declare messages

* pass artifact messages as argument

* filter out empty from unused messages

* filter out empty from unused messages

* infer path from PSScriptRoot; reuse configure in format job

* remove unused messages

* add new line at the end of ps script

* remove unused messages

* try something

* add messages.json again

---------

Co-authored-by: Javier Matos <javiermatos@Javiers-Laptop.local>
Co-authored-by: Javier Matos <javiermatos@Javiers-Laptop.lan>
2024-04-10 19:50:55 -04:00
Billy O'Neal 8a83681f92
Update vcpkg-scripts-sha for 2024-02-06. (#1341)
Also picks up the edit noted by @dg0yt in https://github.com/microsoft/vcpkg/pull/35931#discussion_r1444219371
2024-02-07 01:28:05 +00:00
dan-shaw 692785ac94
Sign Powershell scripts for VS (#451)
* Sign Powershell scripts

* Rename PublishLocation to PublishTo, as requested by Nicole.

* Avoid running NuGet pack if we aren't going to publish

* Explain 'signing type'.

* Ensure the signed ps1s are in all standalone bundle forms.

* Move scripts so that they don't need to be moved again, and publish as part of github releases.

* typo

* Also fix paths in arch-independent-signing.signproj.

* Remove 'scripts' directory name before signing.

* Create staging directory.

* Reference parameters the right way.

* Attempt to reference parameters the right way again.

* Always make the nupkg even when test signing.

Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
2022-03-30 14:26:49 -07:00