Initial action code

.github/workflows/ci.yaml

@@ -0,0 +1,39 @@
+# CI workflow to build and test
+
+name: CI Build & Test
+
+on:
+  # Triggers the workflow on push or pull request events but only for the "main" branch
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: windows-latest
+    strategy:
+      matrix:
+        toolchain:
+          - stable
+    steps:
+      - uses: actions/checkout@v4
+      - uses: microsoft/[email protected]
+      - uses: ./
+      - name: Check MASM Path
+        run: |
+          if (Test-Path env:masmPath) {
+            Write-Output "MASM path is set to: $env:masmPath"
+            if (Test-Path "$env:masmPath\ml64.exe") {
+              Write-Output "ml64.exe found at the specified path."
+            } else {
+              Write-Error "ml64.exe not found at the specified path."
+              exit 1
+            }
+          } else {
+            Write-Error "MASM path environment variable is not set."
+            exit 1
+          }

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [[email protected]](mailto:[email protected]). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,62 @@
+# Contributing to setup-masm
+
+We're excited that you're interested in contributing to setup-masm! This document outlines the process for contributing to this project.
+
+## Code of Conduct
+
+By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). Please read it before contributing.
+
+## How to Contribute
+
+1. **Fork the Repository**: Start by forking the repository to your GitHub account.
+
+2. **Clone the Fork**: Clone your fork to your local machine.
+
+   ```
+   git clone https://github.com/your-username/setup-masm.git
+   ```
+
+3. **Create a Branch**: Create a new branch for your contribution.
+
+   ```
+   git checkout -b feature/your-feature-name
+   ```
+
+4. **Make Changes**: Make your changes or additions to the code.
+
+5. **Test Your Changes**: Ensure that your changes don't break any existing functionality.
+
+6. **Commit Your Changes**: Commit your changes with a clear and descriptive commit message.
+
+   ```
+   git commit -m "Add feature: your feature description"
+   ```
+
+7. **Push to Your Fork**: Push your changes to your fork on GitHub.
+
+   ```
+   git push origin feature/your-feature-name
+   ```
+
+8. **Create a Pull Request**: Go to the original setup-masm repository and create a pull request from your fork.
+
+## Pull Request Guidelines
+
+- Provide a clear title and description for your pull request.
+- Include any relevant issue numbers in the description.
+- Ensure your code follows the existing style of the project.
+- Include tests if you're adding new functionality.
+- Update documentation if necessary.
+
+## Reporting Issues
+
+If you find a bug or have a suggestion for improvement:
+
+1. Check if the issue already exists in the [Issues](https://github.com/owner/setup-masm/issues) section.
+2. If not, create a new issue, providing as much relevant information as possible.
+
+## Questions?
+
+If you have any questions or need further clarification, feel free to open an issue for discussion.
+
+Thank you for contributing to setup-masm!