Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

• .github/workflows/npm-gulp.yml

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process.

The complete list of files we can't accept are:

• .devcontainer/**
• .github/**
• data/reusables/rai/**
• Dockerfile*
• src/**
• package*.json
• content/actions/how-tos/security-for-github-actions/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter type: rai or contentType: rai.

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

🤖 This comment is automatically generated.

This pull request introduces a new GitHub Actions workflow for building Node.js projects with Gulp. The workflow is triggered on pushes and pull requests to the main branch and sets up builds across multiple Node.js versions.

Continuous Integration setup:

• Added a new workflow file .github/workflows/npm-gulp.yml to automate building the project using Node.js and Gulp on pushes and pull requests to the main branch.
• Configured the workflow to run on Ubuntu and test against Node.js versions 18.x, 20.x, and 22.x using a matrix strategy.
• Included steps for checking out the code, setting up the correct Node.js version, installing dependencies, and running the Gulp build process.

@Will100001 Sorry, we don't allow open source contributions on this kind of file. Our documentation is open source, not our workflows or the codebase for the site. We only accept contributions to files inside the "content" folder, and only the markdown files there.