Skip to content

A collection of tools to help with developing extensions for Azure DevOps.

License

Notifications You must be signed in to change notification settings

joachimdalen/azext

Repository files navigation


Logo

AzExt - Azure DevOps Extension Tools

A collection of tools to help with developing extensions for Azure DevOps.
Explore the docs »

View Package · Changelog · Report Bug · Request Feature

Azure DevOps builds
Issues License npm bundle size (scoped) npm (scoped)
Dependent repos (via libraries.io), scoped npm package Libraries.io dependency status for latest release, scoped npm package Snyk Vulnerabilities for npm scoped package
Table of Contents
  1. About The Project
  2. Getting Started
  3. Workboard
  4. Roadmap
  5. Contributing
  6. Contact
  7. License

About The Project

AzExt provides a set of utilities to help with developing Extensions for Azure DevOps.

Getting Started

This is an example of how you may give instructions on setting up your project locally. To get a local copy up and running follow these simple example steps.

Installation

  npm install -g @joachimdalen/azext

Developing

  1. Clone the repo
    git clone https://github.com/joachimdalen/azext.git
  2. Install dependencies
    > npm install
  3. Build package
    > npm run build

(back to top)

Workboard

All issues are manged under the AzExt - Workboard project

  • Triage: These issues and pull requests still needs to be reviewed
  • Planned: These are planned features and bugfixes
  • Specification: These needs additional planning before starting the implementation
  • In Progress: We are working on these
  • Done: There are completed 🚀

(back to top)

Roadmap

See Workboard - Planned (@type/feature) for a full list of proposed features.

(back to top)

Contributing

Contributions are welcome, both in the form of suggestions and code. Create

If you want to contribute code, I ask that you follow some guidelines.

  • New and changed features should to the best ability be covered by tests
  • Follow the branching policy:
    • feature/ for new features
    • bugfix/ for bug fixes
    • docs/ for documentation changes
  • If your change is related to an issue, use the id as the first part of the branch e.g bugfix/12-fix-crash-when-updating-rule
  • Pull requests should target the develop branch
  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

(back to top)

Contact

If you have generic questions about the project or usage you can make contact in the following ways:

(back to top)

License

Distributed under the MIT License. See LICENSE for more information.

(back to top)