Skip to main content

['lammps_step', 'A step in SEAMM Flowchart for LAMMPS simulations', '']

Project description

LAMMPS step

https://img.shields.io/pypi/v/lammps_step.svg https://img.shields.io/travis/molssi-seamm/lammps_step.svg Documentation Status Updates https://codecov.io/gh/molssi-seamm/lammps_step/branch/master/graph/badge.svg

The LAMMPS step for a SEAMM flowchart

Contributing

This project uses the git branching model outlined by Vincent Driessen. Development is handled by branching feature branches from the ‘develop’ branch:

Feature branches

May branch off from:
develop
Must merge back into:
develop
Branch naming convention:
anything except master, develop, release-, or hotfix-

Feature branches (or sometimes called topic branches) are used to develop new features for the upcoming or a distant future release. When starting development of a feature, the target release in which this feature will be incorporated may well be unknown at that point. The essence of a feature branch is that it exists as long as the feature is in development, but will eventually be merged back into develop (to definitely add the new feature to the upcoming release) or discarded (in case of a disappointing experiment).

Feature branches typically exist in developer repos only, not in origin.

Creating a feature branch

When starting work on a new feature, branch off from the develop branch:

$ git checkout -b myfeature develop
Switched to a new branch "myfeature"

Incorporating a finished feature on develop

Finished features may be merged into the develop branch to definitely add them to the upcoming release:

$ git checkout develop
Switched to branch 'develop'
$ git merge --no-ff myfeature
Updating ea1b82a..05e9557
(Summary of changes)
$ git branch -d myfeature
Deleted branch myfeature (was 05e9557).
$ git push origin develop

The –no-ff flag causes the merge to always create a new commit object, even if the merge could be performed with a fast-forward. This avoids losing information about the historical existence of a feature branch and groups together all commits that together added the feature.

Features

  • TODO

Credits

This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.

History

0.1.0 (2017-12-20)

  • First release on PyPI.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for lammps-step, version 0.6
Filename, size File type Python version Upload date Hashes
Filename, size lammps_step-0.6-py2.py3-none-any.whl (61.5 kB) File type Wheel Python version py2.py3 Upload date Hashes View hashes
Filename, size lammps_step-0.6.tar.gz (54.2 kB) File type Source Python version None Upload date Hashes View hashes

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page