GitHub

📥 How to Reset and Start Again Method 1: Reset your current branch This will discard all local changes and make the local branch exactly match the remote. # First, make sure you're on the right branch git checkout release/v3.1.0 # Fetch the latest changes from remote git fetch origin # Reset your local branch to match the remote version git reset --hard origin/release/v3.1.0 Method 2: Fresh checkout (if you want to start completely fresh) # First, move to a safe location (if you have unsaved work) git stash # Then checkout the release branch, forcing a clean copy git checkout -f release/v3.1.0 # Update to the latest version from remote git pull origin release/v3.1.0 ⚠️ Note: Both methods will discard any uncommitted changes! If you have work you want to keep, commit it to a temporary branch first: ...

✅ Daily Git Workflow with Tag Strategy 1. Continue to work on the feature branch git checkout feature/v3.2.0 git pull origin feature/v3.2.0 2. Commit stable changes git add . git commit -m "Fixed export timeout issue" 3. Tag a stable version (optional, when ready) # Use semantic versioning: v3.1.3, v3.1.4, etc. # Tags point to the most recent commit. git tag v3.1.2 4. Push your changes and tag to GitHub git push origin feature/v3.2.0 git push origin v3.1.2 5. Verify your tag (if needed) git tag # List local tags git show v3.1.2 # Show details of the tag git branch --contains v3.1.2 # See which branch includes it Bonus (Optional Advanced Commands) List tags sorted by date (most recent first): ...

Move to “master” Open the terminal (press Ctrl+`) and run: git checkout master If master isn’t checked out locally yet, do: git fetch origin git checkout master If “master” was not updated in the local branch If the branch switched successfully to master, but the files in your working directory didn’t update as expected, it could be one of these cases: Confirm You’re on the Correct Branch Run this to verify: git branch You should see something like this. The asterisk * indicates your current branch. ...

1. Check the connection git remote -v See also: Git - Useful Commands Git - Move Branch Git - Ignore Settings

How to Ignore Uploading Folders and Files to GitHub For example .venv folder Open your project folder in VS Code. Open .gitignore file in the root of the project Add the following line to .gitignore: .venv/ Save the file. then Git will ignore the .venv folder, and it won’t be tracked in your repository. If .venv was already committed before, you’ll need to remove it from Git history using: git rm -r --cached .venv git commit -m "Removed .venv from repository" git push origin main # or your current branch You can check if .venv is ignored by Git using the following command ...