This repo hosts sample workflows to be used with NSP Workflow manager. The repository contains a number of blueprints that can be used as a starting point for your own workflows. The accompanying README files with each workflow detail the purpose of the workflow, installation & execution instructions, NSP requirements and the product set that the workflow was tested against.
Nokia NSP with Workflow Manager
Download the workflow and then use the Workflow Manager workflow Import functionality to import the workflow into your WFM instance.
This project is licensed under the BSD-3 Clause License. See LICENSE.md file for details.
If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about new technologies and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.
Please follow the following instructions:
- Create a personal fork of the project on Github.
- Clone the fork on your local machine. Your remote repo on Github is called
origin
. - Add the original repository as a remote called
upstream
. - If you created your fork a while ago be sure to pull upstream changes into your local repository.
- Create a new branch to work on! Branch from
develop
if it exists, else frommaster
. - Implement/fix your feature, comment your code.
- Follow the code style of the project, including indentation.
- If the project has tests run them!
- Write or adapt tests as needed.
- Add or change the documentation as needed.
- Squash your commits into a single commit with git's interactive rebase. Create a new branch if necessary.
- Push your branch to your fork on Github, the remote
origin
. - From your fork open a pull request in the correct branch. Target the project's
develop
branch if there is one, else go formaster
! - Once the pull request is approved and merged you can pull the changes from
upstream
to your local repo and delete your extra branch(es).
And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.