This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Help us keep this project open and inclusive. Please read and follow our Code of Conduct.
If you find a bug in the source code or a mistake in the documentation, you can help us by submitting an issue to the GitHub Repository. Even better, you can submit a Pull Request with a fix.
You can request a new feature by submitting an issue to the GitHub Repository. If you would like to implement a new feature, please submit an issue with a proposal for your work first, to be sure that we can use it.
- Small Features can be crafted and directly submitted as a Pull Request.
Before you submit an issue, search the archive, maybe your question was already answered.
If your issue appears to be a bug, and hasn't been reported, open a new issue. Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues. Providing the following information will increase the chances of your issue being dealt with quickly:
- Overview of the Issue - if an error is being thrown a non-minified stack trace helps
- Version - what version is affected (e.g. 0.1.2)
- Motivation for or Use Case - explain what are you trying to do and why the current behavior is a bug for you
- Browsers and Operating System - is this a problem with all browsers?
- Reproduce the Error - provide a live example or a unambiguous set of steps
- Related Issues - has a similar issue been reported before?
- Suggest a Fix - if you can't fix the bug yourself, perhaps you can point to what might be causing the problem (line of code or commit)
You can file new issues by providing the above information at the corresponding repository's issues link: https://github.com/[organization-name]/[repository-name]/issues/new].
Before you submit your Pull Request (PR) consider the following guidelines:
- Search the repository (https://github.com/[organization-name]/[repository-name]/pulls) for an open or closed PR that relates to your submission. You don't want to duplicate effort.
- Make your changes in a new git fork
- Follow Code style conventions
- Run the tests (and write new ones, if needed)
- Commit your changes using a descriptive commit message
- Push your fork to GitHub
- In GitHub, create a pull request to the
mainbranch of the repository - Ask a maintainer to review your PR and address any comments they might have
Install the development dependencies:
python3 -m pip install -r requirements-dev.txt
Install the pre-commit hooks:
pre-commit install
Run the tests:
python3 -m pytest
Check the coverage report to make sure your changes are covered.
python3 -m pytest --cov
Install Playwright browser dependencies:
playwright install --with-deps
Run the tests:
python3 -m pytest tests/e2e.py --tracing=retain-on-failure
When a failure happens, the trace zip will be saved in the test-results folder. You can view that using the Playwright CLI:
playwright show-trace test-results/<trace-zip>
You can also use the online trace viewer at https://trace.playwright.dev/
This codebase includes several languages: TypeScript, Python, Bicep, Powershell, and Bash. Code should follow the standard conventions of each language.
For Python, you can enforce the conventions using ruff and black.
Install the development dependencies:
python3 -m pip install -r requirements-dev.txt
Run ruff to lint a file:
python3 -m ruff <path-to-file>
Run black to format a file:
python3 -m black <path-to-file>
If you followed the steps above to install the pre-commit hooks, then you can just wait for those hooks to run ruff and black for you.