-
Notifications
You must be signed in to change notification settings - Fork 70
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'origin/main' into 15785-alt-text-valida…
…tion
- Loading branch information
Showing
278 changed files
with
8,690 additions
and
2,192 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -121,7 +121,6 @@ You can view team sprint boards using either the Github view with Zenhub browser | |
|
||
### Context & History | ||
- [ ] How does the team fit into the larger OCTO ecosystem? [View this Mural diagram](https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1686789362540/fb8f73b8d536f088e56bd3e38f0e37141560f62a?sender=u0b235d03cbd64f7f93673243) | ||
- [ ] Why is VA.gov using a Drupal CMS and how is our success measured? Read the [objectives and key results](https://va-gov.atlassian.net/wiki/spaces/VAGOV/pages/96698383/Product+CMS). | ||
- [ ] [Watch the Drupal GovCon presentation about the project](https://www.youtube.com/watch?v=WN4bGjEuQdM). | ||
- [ ] Why are VA Medical Centers changing their websites? Watch the [2-minute YouTube video](https://youtu.be/Xrv5wCv6cKY). | ||
- [ ] Why are Vet Centers important to Veterans? Watch the [2-minute YouTube video](https://www.youtube.com/watch?v=VMzkZNbKk1I). | ||
|
@@ -183,7 +182,7 @@ Drupal is the VA's content management system of choice. For anyone on our team, | |
- [ ] **Drupal production access**: (SOCKS or VA network required) - in DSVA #cms-support channel, use the Slack workflow to file a helpdesk support request. Ask the helpdesk to create a Drupal user for you in [prod.cms.va.gov](prod.cms.va.gov). | ||
* DevOps team members require an administrator account. (SOCKS or VA access with PIV card required) | ||
* Standard practice for other roles is to have minimal access in prod (content editor or even a blocked account) and full admin access in lower environments. | ||
- [ ] [View short presentations on specific topics](https://va-gov.atlassian.net/wiki/spaces/VAGOV/pages/1714094110/CMS+Topic+Dives). Topics include site alerts, release and deploy, Facility API, etc. | ||
- [ ] [View Topic Dives](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/teams/sitewide/topic-dives) (short presentations on specific topics). Topics include site alerts, release and deploy, Facility API, etc. | ||
- [ ] [Browse the VA Drupal CMS Knowledge Base articles](https://prod.cms.va.gov/help/). | ||
- [ ] What is Drupal? [Link list for Drupal context and community](https://docs.google.com/spreadsheets/d/11ppWiIggKJh-YAWia28utZXW48tJZGCEg-sFJ6eIl9c) | ||
- [ ] If you have a Drupal.org account, add your Agency & VA. Drupal.org > Login > My Account > Edit profile > Work tab > Add your agency, and "Department of Veterans Affairs" & save. This will help our team track Drupal open source contributions. | ||
|
@@ -325,7 +324,7 @@ Each repository includes READMEs to help with setup. | |
- [ ] [Platform Collab Cycle calendar](https://calendar.google.com/calendar/u/0/[email protected]&ctz=America/New_York) | ||
|
||
**CMS Collab Cycle** | ||
- [ ] [CMS Collab Cycle documentation](https://va-gov.atlassian.net/wiki/spaces/VAGOV/pages/1791459333/CMS+Collaboration+Flow#like-section) | ||
- [ ] [CMS Collab Cycle documentation](LINK TBD on CMS provision of Plat Confluence access or migration of docs to DEPO website) | ||
- [ ] [CMS Collab Cycle kanban board](https://github.com/department-of-veterans-affairs/va.gov-cms#workspaces/cms-collaboration-cycle-reviews-62f50368ef32b60022d76d64/board?repos=154174777) | ||
|
||
**Tracking features** | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,79 @@ | ||
|
||
name: "Taxonomy - Update Term" | ||
description: "Use this template when updating an existing terms in the Service or Benefit taxonomy." | ||
title: "[UPDATE] (Term name) in (taxonomy name)" | ||
labels: Content, Content governance | ||
|
||
body: | ||
|
||
- type: dropdown | ||
id: which-taxonomy | ||
attributes: | ||
label: Which Taxonomy is this term for? | ||
multiple: false | ||
options: | ||
- VA Benefits taxonomy | ||
- VA services taxonomy | ||
- Other | ||
validations: | ||
required: true | ||
- type: input | ||
id: term-link | ||
attributes: | ||
label: Link to existing term | ||
description: e.g. https://prod.cms.va.gov/health-care/medical-records | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: rationale | ||
attributes: | ||
label: Rationale for updating this term | ||
description: Write a short explanation of why this term needs to be updated. Include links to any relevant issues, research findings, etc. | ||
validations: | ||
required: true | ||
- type: dropdown | ||
id: products | ||
attributes: | ||
label: Which products will this term impact? | ||
multiple: true | ||
options: | ||
- VAMCs | ||
- Vet Centers | ||
- VBA Regional Office | ||
- Benefit hubs | ||
- Other | ||
validations: | ||
required: false | ||
- type: dropdown | ||
id: stakeholders | ||
attributes: | ||
label: Have stakeholders from impacted products been consulted? | ||
multiple: false | ||
options: | ||
- 'Yes' | ||
- 'No' | ||
validations: | ||
required: true | ||
- type: dropdown | ||
id: subfields | ||
attributes: | ||
label: Have you drafted content for all the relevant subfields? | ||
multiple: false | ||
options: | ||
- 'Yes' | ||
- 'No' | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: acceptance-critera | ||
attributes: | ||
label: Acceptance Criteria | ||
description: Customize the Acceptance Critera or use the default | ||
value: | | ||
- [ ] Content for subfields is drafted in Drupal by Product team | ||
- [ ] Content is reviewed by relevant taxonomy governance body | ||
- [ ] Content is reviewed by relevant stakeholders | ||
- [ ] (List any necessary review and approval steps here) | ||
- [ ] Term is published | ||
validations: | ||
required: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,105 @@ | ||
name: Set Test Statuses | ||
on: | ||
- pull_request_target | ||
permissions: | ||
pull-requests: write | ||
checks: write | ||
contents: write | ||
statuses: write | ||
jobs: | ||
# Tugboat tests are not automatically set pending, even though they are | ||
# required in branch protection rules (see #10553). | ||
# | ||
# Therefore, a PR can inappropriately appear to be ready to merge if, | ||
# for instance, a composer.lock merge conflict prevents the Tugboat | ||
# preview from successfully building. | ||
# | ||
# Additionally, CI tests are only run for code changes but they are | ||
# required checks, even for documentation only changes. In these cases, | ||
# the tests should be skipped since no functional changes have occured. | ||
# | ||
# To address these two issues, this action sets check statuses directly | ||
# to the appropriate states: | ||
# - For docs only changes, all required checks are set to 'success' | ||
# - For code changes, Tugboat tests are set to 'pending' so that we can | ||
# trust our automated code review processes more. | ||
set-test-statuses: | ||
name: Set Tests Statuses | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Check for documentation only changes | ||
id: docs-only | ||
uses: actions/github-script@d7906e4ad0b1822421a7e6a35d5ca353c962f410 # v6.4.1 | ||
with: | ||
script: | | ||
const opts = github.rest.pulls.listFiles.endpoint.merge({ | ||
owner: context.repo.owner, | ||
repo: context.repo.repo, | ||
pull_number: context.payload.pull_request.number, | ||
}) | ||
const files = await github.paginate( | ||
opts, | ||
(response) => response.data.map( | ||
(file) => file.filename | ||
) | ||
) | ||
for (const file of files) { | ||
console.log(`Checking PR file: ${file}`) | ||
if (!file.endsWith('.md')) { | ||
console.log(`Code change found in: ${file}`) | ||
return "false" | ||
} | ||
} | ||
console.log(`No code change found.`) | ||
return "true" | ||
result-encoding: string | ||
- name: Set status for documentation changes. | ||
if: ${{ steps.docs-only.outputs.result == 'true' }} | ||
run: | | ||
test_names=( | ||
va/tests/cypress | ||
va/tests/phpunit | ||
va/tests/content-build-gql | ||
va/tests/status-error | ||
'Composer Validate' | ||
'Check Fields' | ||
ESLint | ||
Stylelint | ||
PHPStan | ||
PHPUnit | ||
PHP_CodeSniffer | ||
'PHP Lint' | ||
) | ||
for test_name in "${test_names[@]}"; do | ||
gh api \ | ||
--method POST \ | ||
-H "Accept: application/vnd.github+json" \ | ||
"/repos/${GITHUB_REPOSITORY}/statuses/${SHA}" \ | ||
-f state='success' \ | ||
-f context="${test_name}"; | ||
done; | ||
env: | ||
SHA: ${{ github.event.pull_request.head.sha }} | ||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
- name: Set status for code changes. | ||
if: ${{ steps.docs-only.outputs.result == 'false' }} | ||
run: | | ||
test_names=( | ||
va/tests/cypress | ||
va/tests/phpunit | ||
va/tests/content-build-gql | ||
va/tests/status-error | ||
) | ||
for test_name in "${test_names[@]}"; do | ||
gh api \ | ||
--method POST \ | ||
-H "Accept: application/vnd.github+json" \ | ||
"/repos/${GITHUB_REPOSITORY}/statuses/${SHA}" \ | ||
-f state='pending' \ | ||
-f context="${test_name}"; | ||
done; | ||
env: | ||
SHA: ${{ github.event.pull_request.head.sha }} | ||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
name: Delete Tugboat Preview | ||
on: | ||
pull_request: | ||
types: | ||
- closed | ||
paths-ignore: | ||
- '**.md' | ||
|
||
jobs: | ||
tugboat_delete_preview: | ||
runs-on: self-hosted | ||
env: | ||
NODE_EXTRA_CA_CERTS: /etc/ssl/certs/ca-certificates.crt | ||
name: Delete Tugboat Preview | ||
steps: | ||
- name: Restore Preview ID | ||
uses: actions/cache/restore@704facf57e6136b1bc63b828d79edcd491f0ee84 # v3.3.2 | ||
with: | ||
path: .tugboat_preview.txt | ||
key: ${{ runner.os }}-tugboat-preview-id-pr-${{ github.event.pull_request.number }} | ||
- name: Set Preview ID | ||
run: | | ||
if ! [ -f .tugboat_preview.txt ]; then | ||
echo "Preview ID not found, please manually delete Tugboat Preview. Contact platform-cms-qa on Github or CMS QA Engineers in #cms-support on Slack for assistance." | ||
exit 1 | ||
fi | ||
PREVIEW_ID=$(cat .tugboat_preview.txt) | ||
echo "Preview ID: ${PREVIEW_ID}" | ||
echo "PREVIEW_ID=$PREVIEW_ID" >> $GITHUB_ENV | ||
- name: Cleanup temporary file | ||
run: rm .tugboat_preview.txt | ||
- name: Delete Tugboat Preview | ||
run: | | ||
curl --fail \ | ||
-H "Authorization: Bearer ${{ secrets.TUGBOAT_API_TOKEN }}" \ | ||
-H "Content-Type: application/json" \ | ||
-X DELETE \ | ||
-d '{ "force": "false" }' \ | ||
https://api.tugboat.vfs.va.gov/v3/previews/${{ env.PREVIEW_ID }} |
Oops, something went wrong.