check
command executes without errors. This is then used by the test command to run the tests incrementally, by only executing the affected tests, which substantially speeds up the tests.stable point in time
is to tag it with git (-f tells git to reuse the tag if already exists):git log --pretty=oneline
again:stable-lisa
. Note that your hash tags will be different and when we refer to e.g. c91fdad
in the following examples, you should instead give your own corresponding hash code.info
command:stable since
hash has been updated and is now tagged with stable-lisa
. All the *
signs are gone because no component
, base
or project
has yet changed since the second commit (which can be verified by running poly diff
again).stable-lisa
but we could have named the tag with anything that starts with stable-
. We choose stable-lisa
because Lisa is our name (let's pretend that at least!). The idea is that every developer could use their own unique tag name that doesn't conflict with other developers.stable-
plus branch name or build number, to mark successful builds. It may be enough to only use the stable points that the CI server creates. That is at least a good way to start out and only add custom tags per developer when needed.workspace.edn
and can be changed if we prefer something else:stable-*
) or if no match was found, the first commit in the repository.deps.edn
file, it got a trailing *
to indicate that it was changed. But what happens if only some of its bricks have changed? Let's try that by adding a comment to the user.core
namespace:info
command again:+
which indicates that the projects themselves are unchanged but that at least one of their bricks has changed.v1.1.0
and the second as v1.2.0
(make sure you replace c91fdad
with your corresponding sha):workspace.edn
:git log --pretty=oneline
we can verify that the tags are correctly set:since
parameter is used by the CI server to run all tests since the previous release, e.g.:release
or previous-release
. If since
is not given, stable
will be used by default.since:e7ebe68
, since:head
, or since:head~1
are also valid.