Scribd Logo
Upload

Welcome to Scribd!

  • 23 views

    Git Challenge

    Uploaded by

    David Fonseca
    The document provides instructions for a Git challenge involving creating a GitHub organization and repository using GitFlow branching strategies. Participants must fork a guide repository, either individually or through the organization's repository, and push feature branches, pull requests, and commits. The goal is to familiarize participants with Git commands, GitHub, organizations, and optional tools like GitFlow. Participants will present their results on January 27th and be evaluated on their repository network graph and ability to discuss the process and Git concepts.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Git Challenge

    Uploaded by

    David Fonseca
    23 views2 pages
    The document provides instructions for a Git challenge involving creating a GitHub organization and repository using GitFlow branching strategies. Participants must fork a guide repository, either individually or through the organization's repository, and push feature branches, pull requests, and commits. The goal is to familiarize participants with Git commands, GitHub, organizations, and optional tools like GitFlow. Participants will present their results on January 27th and be evaluated on their repository network graph and ability to discuss the process and Git concepts.

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides instructions for a Git challenge involving creating a GitHub organization and repository using GitFlow branching strategies. Participants must fork a guide repository, either individually or through the organization's repository, and push feature branches, pull requests, and commits. The goal is to familiarize participants with Git commands, GitHub, organizations, and optional tools like GitFlow. Participants will present their results on January 27th and be evaluated on their repository network graph and ability to discuss the process and Git concepts.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    23 views2 pages

    Git Challenge

    Uploaded by

    David Fonseca
    The document provides instructions for a Git challenge involving creating a GitHub organization and repository using GitFlow branching strategies. Participants must fork a guide repository, either individually or through the organization's repository, and push feature branches, pull requests, and commits. The goal is to familiarize participants with Git commands, GitHub, organizations, and optional tools like GitFlow. Participants will present their results on January 27th and be evaluated on their repository network graph and ability to discuss the process and Git concepts.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 2

    Confidential

    GIT CHALLENGE
    For this challenge, you must create a whole GitFlow branch strategy on GitHub using the
    following guide (Check the README.md)

    OBJECTIVES
    1. Familiarize yourself with most used Git commands.
    2. Familiarize yourself with GitHub
    3. Familiarize yourself with the organizations feature on GitHub
    4. Extra: Familiarize yourself with the Git Flow CLI

    CONSIDERATIONS:
    a) Create as a team a free-plan organization (Creating a new organization from scratch -
    GitHub Docs) choose an interesting name, be creative
    b) As a team you must complete all the steps in the guide, consider which discipline as
    an intern you represent in the team, if you are DevOps or have a Maintainer role
    assigned by your team you will manage the organization’s fork repository, if you were
    not assigned as DevOps and you are a Developer, AM or Tester or MSD you will
    have the role of Developer and for this challenge you will manage your own fork
    repository only.
    c) Maintainers should fork from the guide's git repository git-github-ramp,
    Developers should fork the organization’s repo. All members should make sure to
    set it as public just to continue with the challenge.
    d) For the pull request and approval steps, first configure your repo (either
    organizational or developer’s) to protect branches and configure all permissions and
    access in the fork. Developers must allow the maintainer to read developer’s
    repositories. Maintainers are free to decide how to manage access and permissions
    for the organization’s fork, just make sure developers can create pull requests on
    the organization’s repo.

    1 GIT CHALLENGE
    Confidential

    e) Make commits and push/pull request to the organization’s fork. You, as a team,
    should share the work and do ALL the feature branches instead of picking a single
    artist/band. Don’t create Pull Requests to daafonsecato’s repo because David is not
    going to accept them.
    f) Keep in mind that for Developers the organization’s repo is the source repo.

    upstream https://github.com/source-username/repository-name.git
    origin https://github.com/your-username/repository-name.git
    teammate https://github.com/teammate-username/repository-name.git

    g) If you finish early and the git-github-ramp was too easy your extra challenge is to
    fork the repository called git-github-ramp-extra where you do all the same steps in
    less time but with the tool called git flow along with other commands like rebase, cherry-pick
    and merge.
    h) Keep a clear branch history on your repository. You are allowed to break the golden
    rule of rebase if you need to fix any mistake on the public branches

    If you have any questions about the challenge and you haven't found the answer in the
    bibliography of the Git Basics presentation, don't hesitate to ask David Fonseca or your mentor.

    Evaluation:

    With a presentation you will show the results of this challenge to David Fonseca on 27th
    of January at 10:00 a.m.
    You cannot make any changes to your organization’s repository after 09:00 a.m. on the
    27th of January.
    During the presentation, David will check the network graph of your organization’s fork
    and ask you several questions about the process, so you should be able to answer any
    changes made to your repository and about git concepts.

    Good luck!

    2 GIT CHALLENGE

    You might also like