Brad Warren e9050f1a3c dynamically determine base branch name in mattermost notifications (#10496) ... previously, if we merged a PR into one of our point release branches, the mattermost notification would still say it was merged into main. this PR fixes that you can see me testing this change on my fork with this [workflow file](https://github.com/bmw/letsencrypt/actions/runs/19588662936/workflow#L30) and this [output](https://github.com/bmw/letsencrypt/actions/runs/19588662936/job/56102625766#step:2:4) if this PR is merged, i'll do the same thing in our josepy repo		2025-11-24 13:42:14 -08:00
..
assigned.yaml	update actions in response to pull_request_target concerns (#10490)	2025-11-20 15:09:06 -08:00
merged.yaml	dynamically determine base branch name in mattermost notifications (#10496)	2025-11-24 13:42:14 -08:00
notify_weekly.yaml	update actions in response to pull_request_target concerns (#10490)	2025-11-20 15:09:06 -08:00
review_requested.yaml	update actions in response to pull_request_target concerns (#10490)	2025-11-20 15:09:06 -08:00
stale.yml	[REPO] Modify Stalebot Labels for Better Filters (#10171)	2025-01-31 15:23:10 -08:00