Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/bcdh/lexica-latina
https://github.com/bcdh/lexica-latina
Last synced: 1 day ago
JSON representation
- Host: GitHub
- URL: https://github.com/bcdh/lexica-latina
- Owner: BCDH
- License: cc-by-sa-4.0
- Created: 2019-06-22T15:34:34.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2019-06-29T04:49:01.000Z (over 5 years ago)
- Last Synced: 2024-11-22T21:48:58.744Z (2 months ago)
- Language: XSLT
- Size: 40.1 MB
- Stars: 0
- Watchers: 3
- Forks: 7
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Lexica Latina
## GitHub Workflow
### Setting up Lexica Latina on your computer
1. Install GitHub Desktop on your computer
2. Open GitHub Desktop
3. Sign in with your GitHub credentials
4. Go to https://github.com/BCDH/lexica-latina
5. Fork the repository
5. In the forked repository, click on "Clone or download" then select "Open in Desktop"
6. In GitHub Desktop choose where you want to save the Lexica Latina clone on your computer### Contributing to Lexica Latina
#### First-time contribution
1. **Locate your working copy.**
Go to the folder where you cloned your fork.
2. **Do your work.**
3. **Commit your work.**
This will save your initial work to _your local working copy_.
4. **Push your work.**
This will save your intial work to _your_ fork _remotely_.
5. **Create a pull request.**
This will alert the repository admin person that there are changes that should be merged into the original repository.#### Subsequent contributions
Before you make your next contribution, you have to make sure that your local branch is up to date and in sync with the original repo. Remember, you made a fork off of the original repo at some point, but other people may have contributed to it in the meantime. So it's very important that you follow this procedure _every time_ you start doing work on your branch again.
1. **In GitHub Desktop, in your local working copy, fetch origin.**
This will check whether there were any changes made to _your_ fork _remotely_ (i.e. if you committed and pushed some stuff to your fork from a different computer)
2. **If GitHub Desktop instructs you to pull origin, pull origin.**
This will make sure that _your local_ and _your remote_ files are in sync.
3. **Branch > Merge into current branch > Upstream/master**
This will now, in addition, update _your fork_ with all the contributions that have been merged into the original repo from other forks. Remember, each contributor works in their own fork.
4. **If GitHub Desktop instructs you to push origin, push origin.**
This will make sure that the changes from the original repo, which you've just added to _your local master branch_ in the previous step, will also make it to _your remote master branch_. With your local and remote branches fully updated and sync you can finally get to do your work.
4. **Do your work.**
5. **Commit your work.**
This will save your work to _your local branch_.
6. **Push origin.**
This will save your work to _your remote branch_.
7. **Create a pull request.**
This will alert the repository admin person that there are changes in your fork that should be merged into the original repository.