https://github.com/axross/ciccc-treesandtents
https://github.com/axross/ciccc-treesandtents
Last synced: 7 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/axross/ciccc-treesandtents
- Owner: axross
- License: mit
- Created: 2019-03-20T20:42:21.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2019-04-12T13:58:28.000Z (over 6 years ago)
- Last Synced: 2025-01-21T14:47:20.030Z (9 months ago)
- Language: Java
- Size: 967 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Trees and Tents Puzzle
This repository is the code what members below made as the final project.
- Project Management
- [@axross](https://github.com/axross)
- Development
- [@danismgomes](https://github.com/danismgomes)
- [@EriMiwa](https://github.com/EriMiwa)
- [@SyllindaCardoso](https://github.com/SyllindaCardoso)
(TBD: Description and Screenshot)
## Development Workflows
If you're not sure about these flows, let @axross know!
### Take a Task
1. Choose and open an issue (as task) on the "To Do" column
2. Set assignee to you
3. Link the pull request you make to the issue
### Push the Changes
1. Checkout to a new branch
2. Commit the changes there
3. Push the branch to "remote" (this GitHub repository)
4. Create a new pull request
- It's fine even if you didn't finish what you want to do. In this case, it's appropriate to create it as a "draft" pull request
- **You must make sure code that will be merged to master branch work correctly**
5. Set someone as a reviewer and ask him/her to review the changes with a comment
6. (Reviewer) Review the changes and do "approve" or "request change"
- Approve: when you don't find any problem or question
- Request change: when you find some problem or question
- You should leave comments in the review
7. After the reviewer approved, you will merge the pull request to merge. You **should use "Squash and merge"** instead of just "Merge pull request"
### Discuss
It's pretty much better to discuss it on a GitHub issue if you have anything you want to talk or make sure. Because it's really hard to find later things talked in a chat application.
## License
[MIT](LICENSE)