CodingWonders / CodingWonders/DISMTools

git command to manage repository without UI

Open
#297 0 comments 1 reaction 0 assignees View on GitHub

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

  1. How to clone your Github repository with git command
  2. How to update your Github repositories with git command
  3. 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

Is it ok?

Any addition explanation by you can help translator.

Thanks. KR.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.