#version-control

Implement reproducible research practices throughout project lifecycle. Preregistration: 1. Register study protocol before data collection (OSF, ClinicalTrials.gov). 2. Include hypotheses, methods, analysis plan, sample size justification. 3. Distinguish confirmatory from exploratory analyses. Reproducible workflow: 1. Version control: Git/GitHub for code and document management. 2. Literate programming: R Markdown, Jupyter notebooks combining code and narrative. 3. Environment management: Docker containers, package version recording. 4. Automated reporting: dynamic documents that update with new data. Open data and materials: 1. Data repositories: disciplinary (e.g., ICPSR) or general (OSF, Zenodo). 2. Code sharing: GitHub with clear documentation and README files. 3. Materials sharing: survey instruments, interview guides, stimuli. Transparency reporting: 1. CONSORT for RCTs, STROBE for observational studies. 2. Report all measures, manipulations, exclusions. Publication: preprints for rapid dissemination, open access journals when possible.

Master Git for effective collaboration. Workflow: 1. Feature branches (git checkout -b feature/new-feature). 2. Commit often with clear messages (feat:, fix:, docs:). 3. Pull before push (git pull --rebase). 4. Code review via pull requests. 5. Squash commits before merge. 6. Delete merged branches. 7. Tag releases (v1.0.0). Commit message format: type(scope): subject. Use .gitignore. Never commit secrets. Interactive rebase for clean history (git rebase -i). Resolve conflicts carefully. Use git stash for WIP. Learn: git log, git blame, git bisect. Branching strategies: Git Flow, GitHub Flow.

I accidentally committed sensitive data to my last commit and pushed it to the remote repository. What are the Git commands I need to use to completely remove the sensitive file from the repository's history? Explain each step of the process.

Choose Git workflow for team. Strategies: 1. Git Flow (main, develop, feature, release, hotfix). 2. GitHub Flow (main, feature branches, PR). 3. Trunk-based (short-lived branches, frequent merges). 4. Branch naming conventions. 5. Commit message standards. 6. Pull request templates. 7. Protected branches. 8. Squash vs merge commits. Use GitHub Actions or GitLab CI. Automate what you can.