Make WordPress Core

Opened 22 months ago

Closed 22 months ago

Last modified 22 months ago

#56095 closed task (blessed) (fixed)

Remove unnecessary Slack workflow runs for old branches

Reported by: desrosj's profile desrosj Owned by: desrosj's profile desrosj
Milestone: 6.1 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: has-patch
Focuses: Cc:

Description

In [51934], Slack notifications for GitHub Action workflows were restored for older branches. This was done by adding the workflow_run event to the Slack workflow in trunk, which restored notifications without having to backport anything.

While this works, one downfall of this method is a separate workflow run is created to send notifications for every qualifying workflow that completes. This means there are 2 workflows for every one that runs instead of 1.

It also makes it difficult to track which Slack workflow belongs to a normal workflow run.

The Slack workflow is a reusable one and when used this way, the notifications are done as a part of the original workflow. The 5.9 branch and newer have used it in this way instead on the workflow_run event, and it has worked well.

Let's backport this to the older branches to help limit the noise caused by excessive workflow runs and to simplify the Slack notifications workflow by eliminating any logic specific to the workflow_run event (which has data passed in different ways).

The original work for making the Slack notification workflow a reusable one was done as part of #53363, and initially introduced in [51921].

Change History (83)

This ticket was mentioned in PR #2918 on WordPress/wordpress-develop by desrosj.


22 months ago
#1

This removes the workflow_run event and any related logic from the Slack workflow. The changes required to use the workflow as a callable one in older branches are staged and ready to go. This will avoid having to create a separate workflow run to send Slack notifications for older branches.

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2592 on WordPress/wordpress-develop by desrosj.


22 months ago
#2

Core changesets:
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2895 on WordPress/wordpress-develop by desrosj.


22 months ago
#3

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2896 on WordPress/wordpress-develop by desrosj.


22 months ago
#4

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2897 on WordPress/wordpress-develop by desrosj.


22 months ago
#5

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2898 on WordPress/wordpress-develop by desrosj.


22 months ago
#6

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2899 on WordPress/wordpress-develop by desrosj.


22 months ago
#7

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2900 on WordPress/wordpress-develop by desrosj.


22 months ago
#8

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2901 on WordPress/wordpress-develop by desrosj.


22 months ago
#9

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2902 on WordPress/wordpress-develop by desrosj.


22 months ago
#10

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2903 on WordPress/wordpress-develop by desrosj.


22 months ago
#11

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2904 on WordPress/wordpress-develop by desrosj.


22 months ago
#12

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2905 on WordPress/wordpress-develop by desrosj.


22 months ago
#13

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2908 on WordPress/wordpress-develop by desrosj.


22 months ago
#14

Core changesets:
50446
50473
50704
50796
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2909 on WordPress/wordpress-develop by desrosj.


22 months ago
#15

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2910 on WordPress/wordpress-develop by desrosj.


22 months ago
#16

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2911 on WordPress/wordpress-develop by desrosj.


22 months ago
#17

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2912 on WordPress/wordpress-develop by desrosj.


22 months ago
#18

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2913 on WordPress/wordpress-develop by desrosj.


22 months ago
#19

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2914 on WordPress/wordpress-develop by desrosj.


22 months ago
#20

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2915 on WordPress/wordpress-develop by desrosj.


22 months ago
#21

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2916 on WordPress/wordpress-develop by desrosj.


22 months ago
#22

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2917 on WordPress/wordpress-develop by desrosj.


22 months ago
#23

Core changesets:
50446
50473
50704
50930
51341
51355
51498
51511
51535
51921
51924
51925
51937
52002
52130
52183
52233
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2923 on WordPress/wordpress-develop by desrosj.


22 months ago
#24

Core changesets:
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

This ticket was mentioned in PR #2924 on WordPress/wordpress-develop by desrosj.


22 months ago
#25

Core changesets:
53112
53581
53582

Trac ticket: https://core.trac.wordpress.org/ticket/56095

#26 @desrosj
22 months ago

Another thing to mention about using the Slack workflow as a reusable one is that the workflow is called from a specific branch, tag, or SHA. So future modifications to how the workflow works can be made once to trunk and will automatically apply to all older branches.

#27 @desrosj
22 months ago

In 53591:

Build/Test Tools: Remove the workflow_run event from the Slack notification workflow.

The workflow_run event was added to restore Slack notifications for older branches (5.8 and older) without having to backport any changes while alternate approaches were explored.

The workflow has been tested and refined as a reusable one in trunk, and this approach is superior to the workflow_run event in several ways.

Primarily, the workflow_run event results in a separate workflow run being created for sending Slack notifications after the completion of each workflow triggered by push. When called as a reusable workflow, this does not happen and the additional jobs are instead added to the initial workflow. This makes which jobs are sending notifications for the current workflow more clear, and reduces the amount of noise (less workflow runs overall).

The workflow_run event also makes some data available in different ways than push events. By removing it, much of the logic within the workflow can be simplified.

See #56095.

#28 @desrosj
22 months ago

In 53597:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Merges [51921], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.8 branch.
See #56095.

#29 @desrosj
22 months ago

In 53598:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Merges [50446], [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.7 branch.
See #56095.

#30 @desrosj
22 months ago

In 53599:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Merges [50446], [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.6 branch.
See #56095.

#31 @desrosj
22 months ago

In 53600:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Merges [50446], [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.5 branch.
See #56095.

#32 @desrosj
22 months ago

In 53601:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.4 branch.
See #56095.

#33 @desrosj
22 months ago

In 53602:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.3 branch.
See #56095.

#34 @desrosj
22 months ago

In 53603:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.2 branch.
See #56095.

#35 @desrosj
22 months ago

In 53604:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.1 branch.
See #56095.

#36 @desrosj
22 months ago

In 53605:

Build/Test Tools: Merges typo fix from [51511] missed in previous commit.

Follow up to [53598].

Merges [51511] to the 5.7 branch.
See #56095.

#37 @desrosj
22 months ago

In 53606:

Build/Test Tools: Merges typo fix from [51511] missed in previous commit.

Follow up to [53599].

Merges [51511] to the 5.7 branch.
See #56095.

#38 @desrosj
22 months ago

In 53607:

Build/Test Tools: Merges typo fix from [51511] missed in previous commit.

Follow up to [53600].

Merges [51511] to the 5.5 branch.
See #56095.

#39 @desrosj
22 months ago

In 53608:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 5.0 branch.
See #56095.

#40 @desrosj
22 months ago

In 53609:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.9 branch.
See #56095.

#41 @desrosj
22 months ago

In 53610:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.8 branch.
See #56095.

#42 @desrosj
22 months ago

In 53611:

Build/Test Tools: Remove phpcs job related checks.

PHPCS scanning was added in WordPress 5.1, so the status of those checks should not be checked when passing the workflow results to the Slack notifications workflow.

See #56095.

#43 @desrosj
22 months ago

In 53612:

Build/Test Tools: Remove phpcs job related checks.

PHPCS scanning was added in WordPress 5.1, so the status of those checks should not be checked when passing the workflow results to the Slack notifications workflow.

See #56095.

#44 @desrosj
22 months ago

In 53613:

Build/Test Tools: Remove phpcs job related checks.

PHPCS scanning was added in WordPress 5.1, so the status of those checks should not be checked when passing the workflow results to the Slack notifications workflow.

See #56095.

#45 @desrosj
22 months ago

In 53614:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.7 branch.
See #56095.

#46 @desrosj
22 months ago

In 53615:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50796], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.6 branch.
See #56095.

#47 @desrosj
22 months ago

In 53616:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.5 branch.
See #56095.

#48 @desrosj
22 months ago

In 53617:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.4 branch.
See #56095.

#49 @desrosj
22 months ago

In 53618:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.3 branch.
See #56095.

#50 @desrosj
22 months ago

In 53619:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.2 branch.
See #56095.

#51 @desrosj
22 months ago

In 53620:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.1 branch.
See #56095.

#52 @desrosj
22 months ago

In 53621:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 4.0 branch.
See #56095.

#53 @desrosj
22 months ago

In 53622:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 3.9 branch.
See #56095.

#54 @desrosj
22 months ago

In 53623:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 3.8 branch.
See #56095.

#55 @desrosj
22 months ago

In 53624:

Build/Test Tools: Use the Slack notifications workflow as a reusable one.

This backports several changesets that are required to remove the reliance on the workflow_run event for posting Slack notifications.

The Slack notification workflow will now be called as a reusable one, which has several benefits (see [53591]).

Several other minor GitHub Actions related updates are also being backported in this commit to maintain tooling consistency across branches that still receive security updates as a courtesy when necessary.

Workflows that are not relevant to this branch that were mistakenly backported are also being deleted.

Merges [50473], [50704], [50930], [51341], [51355], [51498], [51511], [51535], [51924], [51925], [51937], [52002], [52130], [52183], [52233], [53112], [53581], [53582], [53592] to the 3.7 branch.
See #56095.

#56 @desrosj
22 months ago

In 53625:

Build/Test Tools: Correct svn:mergeinfo after [53599].

[50446] was mistakenly removed.

See #56095.

#82 @desrosj
22 months ago

  • Resolution set to fixed
  • Status changed from assigned to closed

This ticket was mentioned in Slack in #core by sergey. View the logs.


22 months ago

Note: See TracTickets for help on using tickets.