Skip to content

Latest commit

 

History

History
50 lines (30 loc) · 2.56 KB

README.md

File metadata and controls

50 lines (30 loc) · 2.56 KB

Build Extension

Note: This repository forked from Microsoft since the original has not been updated since some years. I use this to implement certain improvements that I thought would be cool as well as were requested on the original one.

Banner Settings provides a settings pane under Organization Settings to allow Project Collection Administrators to show sitewide banners. Alert your Azure DevOps users to upcoming changes or events without sending out mass emails. Compatible with Azure DevOps Services and Server.

Features

  • Show banners on any page in Azure DevOps.
  • Choose between three types (levels) of messages: Info, Warning, and Error.
  • Choose an expiration date for a message.
  • Include hyperlinks in your banners using markdown syntax like the banner message below.
Windows October Update released! Please visit the [Windows Insider Blog](https://blogs.windows.com/windowsexperience/tag/windows-insider-program/) for more info.

Restrictions

  • Only one banner can be shown at a time to keep the interface clean. Banners are prioritized by level. For example, if you have posted a warning message and an info message, the info message will only be shown after a user closes the warning message, or you delete the warning message.
  • Banners are restricted to a length of thirty words.

Building the project

Just run:

npm run build:dev
npm run package:dev

This produces a .vsix file which can be uploaded to the Visual Studio Marketplace

Publish it to your own publisher by running:

npm run publish:dev

You can then serve the extension locally and visit your newly published dev environment extension using

npm run dev

Contributing

This project welcomes contributions and suggestions.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact Microsoft at [email protected] with any additional questions or comments.

Note: I adopted most of the original contributing guidelines. But I am not responsible for maintaining them.