Skip to content

Conversation

@mjcheetham
Copy link
Member

Add the --ref-format option to the scalar clone command. This will allow users to opt-in to creating a Scalar repository using alternative ref storage backends, such as reftable. Example:

scalar clone --ref-format reftable $URL

Add ability to run Git commands for Scalar by passing a struct strvec
rather than having to use varargs.

Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com>
@mjcheetham mjcheetham requested a review from dscho December 17, 2025 14:12
dscho
dscho previously approved these changes Dec 17, 2025
Copy link
Member

@dscho dscho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will also need a corresponding PR for vfs-2.52.0, unfortunately.

derrickstolee
derrickstolee previously approved these changes Dec 17, 2025
Add the `--ref-format` option to the `scalar clone` command. This will
allow users to opt-in to creating a Scalar repository using alternative
ref storage backends, such as reftable. Example:

  scalar clone --ref-format reftable $URL

Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com>
@mjcheetham
Copy link
Member Author

We will also need a corresponding PR for vfs-2.52.0, unfortunately.

#832

@mjcheetham
Copy link
Member Author

We will also need a corresponding PR for vfs-2.52.0, unfortunately.

Actually.. I guess that we'll just want the 2.52 targeting PR, right? I only target 2.51.2 in this PR since it's the default branch still.

@dscho
Copy link
Member

dscho commented Dec 18, 2025

we'll just want the 2.52 targeting PR, right?

That would at least allow us to use git repo in the tests...

@derrickstolee
Copy link

@mjcheetham: This is something that we could send upstream, too, right?

@dscho
Copy link
Member

dscho commented Dec 18, 2025

This is something that we could send upstream, too, right?

Yes!!!

@dscho
Copy link
Member

dscho commented Jan 8, 2026

I'll just merge this for good luck, too (already merged the corresponding #832).

@dscho dscho merged commit b582424 into microsoft:vfs-2.51.2 Jan 8, 2026
229 of 240 checks passed
Copilot AI added a commit that referenced this pull request Jan 14, 2026
release-winget: use WINGET_CREATE_GITHUB_TOKEN environment variable

According to the winget-create documentation, for CI/CD scenarios it is
recommended to use the WINGET_CREATE_GITHUB_TOKEN environment variable
to pass the token to wingetcreate.exe rather than the -t command-line
flag.

The concern is that command-line arguments might be logged in process
listings, whereas environment variables are more secure as they are not
typically exposed in such listings.

This change:
- Retrieves the token from Azure Key Vault directly into a variable
  using `az keyvault secret show` instead of downloading to a file
- Sets the WINGET_CREATE_GITHUB_TOKEN environment variable
- Removes the -t flag from the wingetcreate.exe submit command
- Removes the need for the token.txt file

Co-authored-by: dscho <127790+dscho@users.noreply.github.com>
Copilot AI added a commit that referenced this pull request Jan 14, 2026
release-winget: use WINGET_CREATE_GITHUB_TOKEN environment variable

According to the winget-create documentation, for CI/CD scenarios it is
recommended to use the WINGET_CREATE_GITHUB_TOKEN environment variable
to pass the token to wingetcreate.exe rather than the -t command-line
flag.

The concern is that command-line arguments might be logged in process
listings, whereas environment variables are more secure as they are not
typically exposed in such listings.

This change:
- Retrieves the token from Azure Key Vault directly into the
  WINGET_CREATE_GITHUB_TOKEN environment variable using
  `az keyvault secret show` instead of downloading to a file
- Removes the -t flag from the wingetcreate.exe submit command
- Removes the need for the token.txt file

Co-authored-by: dscho <127790+dscho@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants