← Back to Recording

Summary

Overview

This session is a hands-on technical demonstration focused on Git workflow setup and authentication troubleshooting, particularly in the context of GitHub. The instructor guides through cloning a repository, creating and pushing a new branch, and resolving common authentication issues that cause blank interfaces or failed operations. The content centers on practical command-line Git operations and verifying access permissions via GitHub AuthApps.

Topic (Timeline)

1. Repository Setup and Authentication Troubleshooting [00:00:46.460 - 00:06:15.900]

  • Instructor addresses issues where repository content appears blank, attributing it to GitHub authentication failures.
  • Emphasizes verifying authentication status via GitHub’s AuthApps settings.
  • Guides user to confirm that the local environment has proper access credentials before proceeding with Git operations.
  • Mentions existing cloned repositories (GetOnFig, GetOnFigEmail, GetOnFigEthernet) as preconditions for the next steps.

2. Branch Creation and Push Workflow [00:06:26.540 - 00:07:11.100]

  • Instructs user to create a new branch using the command git checkout -b <branch-name> (referred to as “dash B”).
  • Confirms successful branch creation in the terminal.
  • Directs user to push the newly created branch to the remote repository.
  • Reiterates that authentication issues are a common cause of workflow failure and advises reauthorizing GitHub access if operations fail.
  • Verifies functionality by observing successful execution of the branch creation and push steps.

3. Confirmation and Closure [00:07:13.560 - 00:14:02.560]

  • Repeated verbal confirmations (“Okay”) indicate completion of steps and transition between tasks.
  • No further technical content is delivered; session ends with routine acknowledgments, suggesting the demonstration is concluded.

Appendix

Key Commands

  • git checkout -b <branch-name> — Create and switch to a new branch.
  • Verify authentication via GitHub → Settings → Applications → Authorized OAuth Apps.

Common Pitfalls

  • Blank repository views in IDEs or terminals due to unauthenticated GitHub access.
  • Failure to push branches when local credentials are invalid or expired.

Actionable Guidance

  • Always check GitHub AuthApps for active permissions before starting Git workflows.
  • If cloning or pushing fails, re-authenticate via GitHub’s web interface rather than retrying commands.