Any contributers need to clone the project, create a new branch where they commit their changes and afterwards create a pull request to get their changes merged into the master branch. The following commands can be executed in a command shell once the git client has been installed.
Create a new directory with a working copy of the master branch
git clone https://github.com/xJREB/service-based-antipatterns.git
git checkout -b your-branch-name
Follow these six easy steps to contribute a new antippatern to the knowledge base of Service-Based Antipatterns.
- Clone the projcet
- Create a new branch
- Copy our antipattern skeleton
./antipatterns/default_antipattern.json
, name it according to your antipattern and make sure to place it in theantipatterns
folder in the project root - Fill out as many fields of the skeleton as you can but make sure the fields
name
,description
andsources
are filled out - If a new source has been added, you need to add the BibTeX key and its "cited by" count from Google Scholar to the file
./assets/sources.json
- Each antipattern should also be tagged with one of the following categories
business
,architecture
, orapplication
(mandatory, single tag only) and with an architectural stylesoa
and/ormicroservices
(optional, multiple tags allowed) - If you want to relate your antipattern to existing ones, you may want to use one of the following default relations
precedes
,relates
, orfollows
. You are also free to add a new relation type - Commit your changes
- Create a pull request on the Service-Based Antipatterns GitHub Repo
Once all the checks on the changes of the pull request have passed, one of the maintainers will merge your changes and they will be available on the website shortly afterwards.
You can execute the following commands on the command line after you cloned the project.
Installs any dependencies to run and build the project.
npm install
Use this to have a live preview for any changes you make to the code.
npm run serve
Run this after you have finalized your changes and make sure there are no errors, otherwise it can not be deployed.
npm run build
This runs a static code analysis and you should make sure there are no warnings or errors.
npm run lint