diff --git a/.cspell.json b/.cspell.json index 8391504e..eaa3fc6a 100644 --- a/.cspell.json +++ b/.cspell.json @@ -4,11 +4,17 @@ "ignorePaths": ["node_modules/**", "styles.**"], "words": [ "Allstar", + "APPSW", + "CAIO", "CISA", + "CISO", + "DATAMGT", + "DEIA", "FASC", "FISMA", "Grype", "HSPD", + "INET", "INFOSEC", "ISSM", "ISSO", @@ -16,6 +22,7 @@ "LUOTR", "Nygard", "OPM", + "PLCYPLN", "SDLC", "SYSANALYSIS", "Snyk", @@ -23,6 +30,7 @@ "USDA", "USGSATTS", "USWDS", + "architecting", "automations", "browsersync", "captioner", @@ -34,12 +42,15 @@ "exfiltrate", "frontmatter", "hotfixes", + "inclusivity", "jointts", "neurodiversity", "ohrm", "outdir", + "payrange", "pdate", "refactorization", + "roadmapping", "roadmaps", "sidenav", "signup", @@ -54,6 +65,7 @@ "timeframe", "toolkit", "toolkits", + "touchpoints", "transformative", "usda", "uswds", diff --git a/.github/workflows/protect_main_branch.yml b/.github/workflows/protect_main_branch.yml new file mode 100644 index 00000000..0c4f398e --- /dev/null +++ b/.github/workflows/protect_main_branch.yml @@ -0,0 +1,25 @@ +--- +name: Main Branch Protection + +# yamllint disable-line rule:truthy +on: + pull_request: + branches: + - main + +permissions: read-all + +concurrency: + group: ${{ github.ref }}-${{ github.workflow }} + cancel-in-progress: true + +jobs: + protect-main-branch: + runs-on: ubuntu-latest + steps: + - name: Check branch + run: | + if [[ ${GITHUB_HEAD_REF} != staging ]] ; then + echo "Error: Pull requests to 'main' must come from 'staging'" + exit 1 + fi diff --git a/.markdownlint.json b/.markdownlint.json new file mode 100644 index 00000000..ee967de3 --- /dev/null +++ b/.markdownlint.json @@ -0,0 +1,29 @@ +{ + "blanks-around-fences": false, + "blanks-around-headings": false, + "blanks-around-lists": false, + "code-fence-style": false, + "emphasis-style": false, + "heading-start-left": false, + "hr-style": false, + "list-indent": false, + "list-marker-space": false, + "no-blanks-blockquote": false, + "no-hard-tabs": false, + "no-missing-space-atx": false, + "no-missing-space-closed-atx": false, + "no-multiple-blanks": false, + "no-multiple-space-atx": false, + "no-multiple-space-blockquote": false, + "no-multiple-space-closed-atx": false, + "no-trailing-spaces": false, + "ol-prefix": false, + "strong-style": false, + "ul-indent": false, + "MD013": { + "line_length": 999, + "heading_line_length": 999, + "code_block_line_length": 999 + }, + "MD041": false +} diff --git a/.markdownlint.yaml b/.markdownlint.yaml deleted file mode 100644 index 26ecc390..00000000 --- a/.markdownlint.yaml +++ /dev/null @@ -1,28 +0,0 @@ ---- -blanks-around-fences: false -blanks-around-headings: false -blanks-around-lists: false -code-fence-style: false -emphasis-style: false -heading-start-left: false -hr-style: false -list-indent: false -list-marker-space: false -no-blanks-blockquote: false -no-hard-tabs: false -no-missing-space-atx: false -no-missing-space-closed-atx: false -no-multiple-blanks: false -no-multiple-space-atx: false -no-multiple-space-blockquote: false -no-multiple-space-closed-atx: false -no-trailing-spaces: false -ol-prefix: false -strong-style: false -ul-indent: false - -MD013: - line_length: 999 - heading_line_length: 999 - code_block_line_length: 999 -MD041: false diff --git a/pages/jointts/positions/TTS-Sr-Advisor-Technology.md b/pages/jointts/positions/TTS-Sr-Advisor-Technology.md index 77eafd82..7295ded3 100644 --- a/pages/jointts/positions/TTS-Sr-Advisor-Technology.md +++ b/pages/jointts/positions/TTS-Sr-Advisor-Technology.md @@ -50,7 +50,7 @@ external_url: # To show the alert keyword association message, add the keywords separated by a semi-colon # e.g. Product Management; Strategy/Consulting; and Marketing status_alert: true -alert_keywords: "Executive Managament; Software Engineering; Cloud Architecture; Cloud Engineering; and Cybersecurity" +alert_keywords: "Executive Management; Software Engineering; Cloud Architecture; Cloud Engineering; and Cybersecurity" # If this listing has been updated since it was published, put the updated date below in YYYY-MM-DD format. updated: diff --git a/pages/jointts/positions/USDC-fellow-supe-14.md b/pages/jointts/positions/USDC-fellow-supe-14.md index 69e7f0ec..356b2c0b 100644 --- a/pages/jointts/positions/USDC-fellow-supe-14.md +++ b/pages/jointts/positions/USDC-fellow-supe-14.md @@ -128,7 +128,7 @@ info_sessions: # Make sure to leave the | on the first line. Begin your text by returning to the next line and # indenting once. role_summary: | - The U.S. Digital Corps (USDC) is a new two-year fellowship for early-career technologists to launch impactful careers in public service and create a more effective, equitable government. USDC pairs early-career and highly-skilled, mission-driven software engineers, data scientists, product managers, designers, and cybersecurity specialists with top technology changemakers in the federal government to build human-centered solutions to some of our nation’s toughest challenges. Our Fellows are the engines on projects that create change in the areas of climate, healthcare, racial equity, immigration, economic recovery, and open innovation. The Digital Corps was launched in August 2021 by GSA in partnership with the White House, CISA, and OPM. + The U.S. Digital Corps (USDC) is a new two-year fellowship for early-career technologists to launch impactful careers in public service and create a more effective, equitable government. USDC pairs early-career and highly-skilled, mission-driven software engineers, data scientists, product managers, designers, and cybersecurity specialists with top technology change-makers in the federal government to build human-centered solutions to some of our nation’s toughest challenges. Our Fellows are the engines on projects that create change in the areas of climate, healthcare, racial equity, immigration, economic recovery, and open innovation. The Digital Corps was launched in August 2021 by GSA in partnership with the White House, CISA, and OPM. # Make sure to leave the | on the first line. Begin your text by returning to the next line and # indenting once. diff --git a/pages/jointts/positions/login-data-engineer-2024.md b/pages/jointts/positions/login-data-engineer-2024.md index b65e6c3f..67ccd7b4 100644 --- a/pages/jointts/positions/login-data-engineer-2024.md +++ b/pages/jointts/positions/login-data-engineer-2024.md @@ -59,7 +59,7 @@ updated: # The basic information and details of the position info_intro: Open to U.S. citizens or nationals (residents of American Samoa and Swains Island). Subject to background check. -supervisory_status: non-supervisory +supervisory_status: Non-Supervisory usajobs_official_title: IT Specialist (APPSW/INFOSEC) @@ -132,7 +132,7 @@ role_summary: | This opportunity is located in the Technology Transformation Services (TTS) Solutions Division’s Login.gov team. The Login.gov team is a remote organization and is composed of experts across product development, software engineering, cybersecurity, and platform engineering. - As a Data Engineer at Login.gov, you will provide technical guidance and lead implementation on a cross-functional team building out new, secure data products in support of a diverse set of stakeholders on the Login.gov program, including delivery, security, anti-fraud, and compliance functions. You will work closely with other members of the delivery team, including product, UX, and other engineers to define, implement, and maintain data tooling and infrastructure such as data warehousing solutions, ETL pipelines, data quality tools, and dashboarding and reporting tools. + As a Data Engineer at Login.gov, you will provide technical guidance and lead implementation on a cross-functional team building out new, secure data products in support of a diverse set of stakeholders on the Login.gov program, including delivery, security, anti-fraud, and compliance functions. You will work closely with other members of the delivery team, including product, UX, and other engineers to define, implement, and maintain data tooling and infrastructure such as data warehousing solutions, ETL pipelines, data quality tools, and dashboard and reporting tools. # Make sure to leave the | on the first line. Begin your text by returning to the next line and # indenting once. @@ -142,7 +142,7 @@ qualifications: | # indenting once. specialized_requirements: | - Applying data engineering and information security principles, methods, standards, and practices to program operations. - - Utilizing various analytical and statistical software to prepare data for analysis and clean data to include from structured/semistructured/unstructured sources. + - Utilizing various analytical and statistical software to prepare data for analysis and clean data to include from structured/semi-structured/unstructured sources. - Working with various stakeholders and clients to define and determine the appropriate data services or tools requirements for projects. - Providing technical expertise on the restructuring and/or re-architecting of program data collection storage to assess potential threats, vulnerabilities, and risks. - Using software and programming languages (such as R, Python, SQL) and other tools to conduct operational data engineering functions.