I believe this will be included in actions.json and called via scheduling in cron.yml

this will use shipitscript and treescript tasks to do the following (or something like it):

1. shipitscript task to determine most recent rev shipped. output rev
2. treescript task to determine most recent shippable checked-in rev and if that is newer than most recent shipped rev. output rev
3. shipitscript task to take the treescript task and create a new release in shpii
4. shipitscript task to trigger a phase off the newly created release

these 4 tasks themselves are being tracked in: https://github.com/orgs/mozilla-releng/projects/2?add_cards_query=is%3Aopen

Discussed in person on Monday,

We'll be doing here:

• Decision Task -> Target Tasks Method -> Run only a single shipitscript task

The shipitscript task will trigger the phase via ship-it itself.

In the future when we are able to have a public shipit endpoint we can modify to make this an action task that can call shipitscript to just trigger the release, rather than needing to leave the behavior logic in shipitscript itself.

WIP - Needs a clearer payload

https://hg.mozilla.org/mozilla-central/rev/be119441113b