https://github.com/fluentcodes/gitsamples
GitSamples using Topic Branches for different topics like Java/JavaScript/Node/SpringBoot. Actually a container for own experiments but open for collaboration.
https://github.com/fluentcodes/gitsamples
Last synced: 3 months ago
JSON representation
GitSamples using Topic Branches for different topics like Java/JavaScript/Node/SpringBoot. Actually a container for own experiments but open for collaboration.
- Host: GitHub
- URL: https://github.com/fluentcodes/gitsamples
- Owner: fluentcodes
- Created: 2020-09-03T06:56:50.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2022-04-13T04:30:31.000Z (about 3 years ago)
- Last Synced: 2025-01-07T12:15:43.638Z (4 months ago)
- Homepage:
- Size: 253 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Topic Branch: Master
The **GitSamples** repository contains a mix of Topic Branches which are not handled in other GitSample Topic Repositories
GitSamples
* gather codes from experiment in working tests
* handle different environments in **topic branches**
* document it directly in README.md within Topic Packages
* share it with others
You find only this README on this master **Topic Branch**.
## Other GitSamples
* [GitSamples-Java](https://github.com/fluentcodes/GitSamples-Java): All around java with emphasis on [Java-8](https://github.com/fluentcodes/GitSamples-Java/tree/java-8) and [Design Pattern](https://github.com/fluentcodes/GitSamples-Java/tree/java-design-pattern)
* [GitSamples-GIT](https://github.com/fluentcodes/GitSamples-GIT): Git samples with test branches for own experiments.
* [GitSamples-Spring](https://github.com/fluentcodes/GitSamples-Spring): Spring Topic Branches
* [GitSamples-Java-Libs](https://github.com/fluentcodes/GitSamples-Java-Libs): Topic Branches for different Java Libs
## Intention
The intention of GitSamples is to be a kind of memory for experiments, when one need to get into a special topic. Sometimes
frameworks or languages don't work as one expect or a non working solution is published.
Hopefully one find a solution at the end. But the pitfalls, others can fall into too, are lost. One can see this with a lot of
answers on [stackoverflow](https://stackoverflow.com).
* learning from solutions that doesn't work
* add code in a structured manner
* solutions that hopefully immediately work
* free (wiki) documentation from code snippets
With this sandbox repository I just cleaned up some other sandboxes I had before with the concept of the topic map.
The external wiki is the wiki of github.
I filled it initially with some content, but not all.
## Analysis on [GitSamples-GIT](https://github.com/fluentcodes/GitSamples-GIT)
* [Create new Topic Branches with a Clean History](https://github.com/fluentcodes/GitSamples-GIT/tree/switch-orphan-readme)
* [Behaviour of Markdown Link in Github](https://github.com/fluentcodes/GitSamples-GIT/tree/github-readme-links)
* [Automate Git with Aliases](https://github.com/fluentcodes/GitSamples-GIT/tree/automate-git)
### Links
* https://codingsight.com/git-branching-naming-convention-best-practices/
* https://stackoverflow.com/questions/7653483/github-relative-link-in-markdown-file
* https://levelup.gitconnected.com/what-every-good-readme-should-contain-d6a07d1b39f