a89695c4c5
This should remove the ambiguity on where buildkite.yml should show up at least. We might still want to move workspace.josh into tvix/ too at some point, but that's blocked on https://github.com/josh-project/josh/issues/1287 This commit doesn't cause any change in views/tvix, with a previous version of this commit added to my HEAD, I ran josh-filter to verify it still points to ce0df88561fee8a4d6052ca9f2a1792f899a202a. Change-Id: Ic03e92260dc7725bc2fcf01b7c72a097d92c028e Reviewed-on: https://cl.tvl.fyi/c/depot/+/9828 Reviewed-by: tazjin <tazjin@tvl.su> Tested-by: BuildkiteCI Autosubmit: flokli <flokli@flokli.de> |
||
---|---|---|
.. | ||
kit | ||
tvix | ||
.skip-subtree | ||
default.nix | ||
README.md |
depot views
This folder contains external views of depot content, defined using josh workspaces. See the individual views for a description of their individual content and usage information.
Testing changes locally
Generally, when iterating on these files, it's best to locally invoke josh- filter
(from //third_party//josh
) locally to inspect how the workspace would
look like:
- Commit your changes. This is required, as
josh-filter
operates on yourHEAD
, not working directory state. - Invoke
josh-filter
with the filter expression, for examplejosh-filter ':workspace=views/tvix'
. - Peek at the synthesized git history by looking at
FILTERED_HEAD
.
Testing changes in Gerrit
It's also possible to clone resulting workspaces for CLs that were already pushed to Gerrit, but didn't land in master yet.
For CL1234 at revision 2, the URL passed to git clone
would look like this:
https://code.tvl.fyi/depot.git@refs/changes/32/1234/2:workspace=views/kit.git