CodingWonders / CodingWonders/DISMTools
git command to manage repository without UI
Nobody has claimed this yet.
- Dominant language
- Visual Basic .NET
- Stars
- 1.5k
- Forks
- 72
- Avg merge
- 11m
- Merged PRs (30d)
- 4
Description
@CodingWonders
In your documentation there are the info how to propose pullup requests using fork but using web broser and UI.
I beleieve that when you should made some mass changes to translation where you can use search/replace on different file/strings could be usefull use local file/folder structure (local branches on computer) and use command line.
Then I ask you if you add some info how to do that
- How to clone your Github repository with git command
- How to update your Github repositories with git command
- How to switch to dt_prelel_xxxx with git command
When I will be ready after chages I mae a fork with UI and merge pull request with drag and drop from local pc repository to web UI.
- Clone repository
git clone https://github.com/CodingWonders/DISMTools.git - Clone branches
- Update local repository from remote
git fetch
- Switch branch
git checkout dt_prerel_25111
-
make changes files
-
Create pullup request
git push https://github.com/CodingWonders/DISMTools dt_prerel_25111
Is it ok?
Any addition explanation by you can help translator.
Thanks. KR.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No documentation file or test is named. Review the existing fork and pull-request instructions first, then document the requested command-line workflow: cloning, fetching updates, switching to a branch, making changes, and pushing for a pull request. Done means translators can follow the steps without relying on the web UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100