Skip to content

sonic-net/sonic-buildimage

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date
Dec 7, 2017
May 22, 2019
Apr 3, 2019
May 22, 2019
Aug 9, 2018
Aug 19, 2018
Mar 7, 2019
Mar 29, 2018
Aug 27, 2018
Oct 2, 2017
Aug 27, 2018
Apr 25, 2019
May 16, 2018
May 29, 2019
Oct 22, 2018
May 31, 2019
Apr 24, 2019
May 22, 2019
Oct 2, 2017
Apr 15, 2019
Mar 29, 2017
Mar 2, 2017
Sep 19, 2018
Jul 14, 2017
Sep 19, 2018
Mar 22, 2019
Apr 30, 2019
Mar 1, 2017

Repository files navigation

SONiC: Software for Open Networking in the Cloud

sonic-utilities

Command-line utilities for SONiC

How to run unit test

python2 -m py.test -v

Contribution guide

All contributors must sign a contribution license agreement (CLA) before contributions can be accepted. This process is now automated via a GitHub bot when submitting new pull request. If the contributor has not yet signed a CLA, the bot will create a comment on the pull request containing a link to electronically sign the CLA.

GitHub Workflow

We're following basic GitHub Flow. If you have no idea what we're talking about, check out GitHub's official guide. Note that merge is only performed by the repository maintainer.

Guide for performing commits:

  • Isolate each commit to one component/bugfix/issue/feature
  • Use a standard commit message format:
[component/folder touched]: Description intent of your changes

[List of changes]

Signed-off-by: Your Name [email protected]

For example:

swss-common: Stabilize the ConsumerTable

* Fixing autoreconf
* Fixing unit-tests by adding checkers and initialize the DB before start
* Adding the ability to select from multiple channels
* Health-Monitor - The idea of the patch is that if something went wrong with the notification channel, 
  we will have the option to know about it (Query the LLEN table length).
  
  Signed-off-by: John Doe [email protected]
  • Each developer should fork this repository and add the team as a Contributor
  • Push your changes to your private fork and do "pull-request" to this repository
  • Use a pull request to do code review
  • Use issues to keep track of what is going on