Skip to content

Number the post-change job and group both jobs with the workshop - #33

Merged
bradh11 merged 1 commit into
mainfrom
chore/number-the-post-change-job
Sep 21, 2026
Merged

bradh11 merged 1 commit into
mainfrom
chore/number-the-post-change-job

Conversation

@bradh11

@bradh11 bradh11 commented Sep 11, 2026

Copy link
Copy Markdown
Collaborator

The workshop's Nautobot jobs now sit under one grouping, Arista Lifecycle Workshop, with a two-digit step in each name so the Jobs list reads as the run of show. This repository's two git-synced jobs follow: Arista AVD Post Change Validation becomes 06 Post Change Validation and both it and Load AVD Change Report move into that grouping. Class paths do not change, so the workshop's seed keeps enabling them by path.

After merging, move the baseline tag onto the squash commit (git tag -f baseline <sha> && git push -f origin baseline); the message below ends with the marker so the tag's tip keeps the deploy from firing on a reset.

[skip ci]

@bradh11
bradh11 merged commit cd402fe into main Sep 21, 2026
3 checks passed
@bradh11
bradh11 deleted the chore/number-the-post-change-job branch September 21, 2026 01:50
bradh11 added a commit that referenced this pull request Sep 21, 2026
The \`baseline\` tag has to be the from-nothing state the workshop
resets to: BLUE and GREEN tenants only, with everything AVD builds from
them. Merging #33 on top of the RED change (#32 and its report commit)
left \`main\` carrying RED, so a baseline publish would open a "remove
RED" pull request instead of reporting no changes.

This puts every file under \`sites/\` back to what the previous baseline
(104c832) had and keeps the numbered jobs from #33. After the squash
merge, \`baseline\` moves onto the squash commit.

[skip ci]
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.

1 participant