Foundation laid! #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Created Task entity and implemented endpoint controller * Integrated Priority attributed with Task * Integrated comment association with tasks
* [fix] Task entity and Comment entity to comply with DB. * [fix] Delete methods working fine. * [feat] Custom value-based priority input enabled
* [setup] Separate properties for unit tests defined * Create build.yml * Create unitTests.yml * Modified unitTests.yml * Merged workflows for build and tests * Cached gradle dependencies * Seggregated workflows * Fixed unitTest workflow * Configured trigger events for workflows
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The base structure for the back end is ready.
From, this point, the repo will diversify to support different environments on different branches.
The major areas for diversification would include:
Nomenclature for branches: (main branch would not be affected)
<db-service name>/<branch name>[following general guidelines]e.g. -
main --> mysql/dev --> mysql/setup/dockerFor multiple contributors/collaborators, nomenclature would also include their names :
(except dev branch, of course)
<db-service name>/<collaborator name>/<branch name>e.g. -
main --> mysql/dev --> mysql/rish/setup/dockerThe nomenclature might be changed, to support diversification based on hosting platforms as well