CheapTripAngularClient

Versioning conventions
Dev - dx.x.x
Release - rx.x.x
Master - x.x.x

For Testers

When a new issue is found

Create a new issue here:
https://github.com/talmantel/CheapTripAngularClient/issues/new
Make sure to add appropriate labels including:

• bug
• display: desktop
• display: mobile
• version: {version number} (example: "version: d0.0.1")

Assign Olga (OlgaZaleskovskaya) or any developer if you know who is reponsible for resolving the issue

When a new version is released

Use this link to see non-verified closed issues:
https://github.com/talmantel/CheapTripAngularClient/issues?q=is%3Aissue+-label%3Averified+state%3Aclosed
To verify an issue was resolved, add the label 'verified' to it.
If the issue was not resolved, reopen the issue.

For Developers

Main Branches

• Dev - main development branch. All new features and all bugs for current version should be done here
• Release - once development of current version is done, Dev is merged into release for testing and final bugfixes
• Master - once testing on release branch is done, release is merged into master to be deployed in production

Development

• Create a new branch from dev\release\master, name it with the feature or bug you are dealing with
• Develop...
• Merge remote dev\release\master branch into your branch
• Push your branch to remote
• Create a pull request: https://github.com/talmantel/CheapTripAngularClient/pull/new/your_branch_name into dev\release\master

Resolving issues

Link to issues fixed in a specific pull request or commit by typing "Resolves: #{issue number}" in your pull request description or commit message
For example "Resolves: #123"
For more details see https://docs.github.com/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords

You can also see open issues assigned to you here: https://github.com/talmantel/CheapTripAngularClient/issues/assigned/@me
And comment \ close etc.