immencers' desk

Welcome to immencers' Project Management tools.

Basic PM Guidelines,

1. Create a small issue that can be completed in minimum 15 minutes to a maximum of 4 to 8 hours. Do not create an issue which can take more than eight hours to complete.
2. Before you start working on an issue, always set the status to In Progress and add an Estimated Time.
3. Whenever an issue is solved, change status to Completed, add Progress % and always include Spent Time along with the appropriate notes.
4. If an issue isn't finished on the same day, make sure to update the Progress % and include the Spent Time for that day along with the appropriate notes.
5. Always update PM before walking away from the desk.

Default Commit Formats

<type>(<optional scope>): <subject>
empty separator line
<optional body>
empty separator line
<optional footer>

Examples

feat#9(shopping cart): add education fields into employee form

feat#09: add education fields into employee form

feat(shopping cart): add education fields into employee form

feat: add education fields into employee form

refers to JIRA-1337
BREAKING CHANGES: urlendpoints also changed to v2.

Types

• API relevant changes
  • feat Commits, that adds a new feature
  • fix Commits, that fixes a bug
• refactor Commits, that rewrite/restructure your code, however does not change any behaviour
  • perf Commits are special refactor commits, that improve performance
• style Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc)
• test Commits, that add missing tests or correcting existing tests
• docs Commits, that affect documentation only
• build Commits, that affect build components like build tool, ci pipeline, dependencies, project version, ...
• ops Commits, that affect operational components like infrastructure, deployment, backup, recovery, ...
• chore Miscellaneous commits e.g. modifying .gitignore