Skip to content

TravisWheelerLab/release-workflow-example

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Project

REPLACE: One sentence description of the project.

About

REPLACE: Describe your project in more detail. What does it do? Who are the intended users? Why is it important or meaningful? How does it improve upon similar software? Is it a component of or extension to a larger piece of software?

Installation

REPLACE: How does on install the software? What are the dependencies, if any? Is there a Docker image or installation package of some sort?

Usage

REPLACE: How is the software run (or consumed, for libraries)? Are there any command line flags the user should know about? What do they do, exactly? What do the input data look like? Are there special file formats in use, what are they? What does the output look like?

Development

REPLACE: What language(s) are in use? What does a user need to install for development purposes? This might include build systems, Docker, a particular compiler or runtime version, test libraries or tools, linters, code formatters, or other tools. Are there any special requirements, like processor architecture? What commands should developers use to accomplish common tasks like building, running the test suite, and so on?

Contributing

We welcome external contributions, although it is a good idea to contact the maintainers before embarking on any significant development work to make sure the proposed changes are a good fit.

Contributors agree to license their code under the license in use by this project (see LICENSE).

To contribute:

  1. Fork the repo
  2. Make changes on a branch
  3. Create a pull request

License

See LICENSE for details.

Authors

REPLACE: Who should people contact with questions?

See AUTHORS the full list of authors.

About

Example of tags triggering github actions to create releases

Resources

License

Stars

Watchers

Forks

Packages

No packages published