famous-river-94971
01/12/2023, 8:28 PM--changed-since on main branches after a PR is merged? For example, with this workflow:
1. A PR is opened, we can use --changed-since=origin/main to detect everything that's new on the PR.
2. The PR is merged to main. We want to run a command with effectively the same files that "changed-since" on the PR, but we can't use origin/main anymore.
A few thoughts in the š§µfamous-river-94971
01/12/2023, 8:28 PMHEAD~1famous-river-94971
01/12/2023, 8:29 PMmain that the last successful deployment happened.famous-river-94971
01/12/2023, 8:29 PMlerna and it automatically creates a "release commit" with tags that it uses internally to track this.curved-television-6568
01/12/2023, 8:29 PMfamous-river-94971
01/12/2023, 8:30 PMfamous-river-94971
01/12/2023, 8:30 PMfamous-river-94971
01/12/2023, 8:31 PMcurved-television-6568
01/12/2023, 8:35 PMfamous-river-94971
02/09/2023, 3:25 PM