feanil
diff --git a/‎.github/workflows/send-prs-to-how-how-we-work-boards.yml‎
Lines changed: 45 additions & 0 deletions b/‎.github/workflows/send-prs-to-how-how-we-work-boards.yml‎
Lines changed: 45 additions & 0 deletions
diff --git a/‎assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png‎
38.6 KB b/‎assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png‎
38.6 KB
diff --git a/‎assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png‎
46.4 KB b/‎assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png‎
46.4 KB
diff --git a/‎assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png‎
184 KB b/‎assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png‎
184 KB
diff --git a/‎assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png‎
43.9 KB b/‎assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png‎
43.9 KB
diff --git a/‎assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png‎
230 KB b/‎assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png‎
230 KB
diff --git a/‎assets/images/help/notifications-v2/mobile-watch-settings.png‎
-31.7 KB b/‎assets/images/help/notifications-v2/mobile-watch-settings.png‎
-31.7 KB
diff --git a/‎assets/images/help/repository/code-scanning-alerts-found-link.png‎
11.1 KB b/‎assets/images/help/repository/code-scanning-alerts-found-link.png‎
11.1 KB
diff --git a/‎assets/images/help/repository/code-scanning-branch-dropdown.png‎
-27 KB b/‎assets/images/help/repository/code-scanning-branch-dropdown.png‎
-27 KB
diff --git a/‎assets/images/help/repository/code-scanning-branch-filter.png‎
-46.9 KB b/‎assets/images/help/repository/code-scanning-branch-filter.png‎
-46.9 KB
@@ -0,0 +1,45 @@
+name: Send pull_request to How We Work Boards
+
+# **What it does**: This sends pull requests with the feature label to the Docs Engineering feature board
+# **Why we have it**: If we use PRs to track features this automates them ending up on the feature board
+# **Who does it impact**: Docs Engineering team members
+
+on:
+  pull_request:
+    types:
+      - labeled
+      - opened
+      - reopened
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    steps:
+      - if: (github.repository == 'github/docs-internal' || github.repository == 'github/docs') && (contains(github.event.pull_request.labels.*.name, 'engineering') && contains(github.event.pull_request.labels.*.name, 'feature'))
+        uses: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9
+        with:
+          github-token: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}
+          script: |
+            // Only do this for work by the engineering folks since multiple teams do work
+            // in the docs repos
+            try {
+              await github.teams.getMembershipForUserInOrg({
+                org: 'github',
+                team_slug: 'docs-engineering',
+                username: context.payload.sender.login,
+              });
+            } catch(err) {
+              return
+            }
+
+            var column_id = 13445681;
+            try {
+              github.projects.createCard({
+                column_id: column_id,
+                content_id: context.payload.pull_request.id,
+                content_type: "PullRequest"
+              });
+            } catch (error) {
+              console.log(error);
+            }