course-dprep/team-project-dprep_group6

Migrating Source Code Files to GitHub

Closed this issue · 2 comments

Commit Source Code to GitHub

Now that our files are organized, the next step is to migrate our source code files to GitHub. This process will involve setting up a .gitignore file to exclude unnecessary files (e.g., data files) and committing our source code to the repository.

Objective:

Migrate all source code files to GitHub while excluding data files.

Deliverable:

  • Create new branch in which you commit all files; then, create a pull request. The issue is successfully completed when the pull request is merged.

Instructions:

ONLY ONE TEAM MEMBERS handles the migration. Others can watch and give feedback/help.

  1. Setting Up .gitignore:

    • In your repository's root directory, create a file named .gitignore.
    • Inside .gitignore, list the types of files you wish to exclude from the repository (e.g., *.csv, *.xls, and any other non-source code files).
    • This step prevents unnecessary files from being tracked by Git and keeps the repository clean.
  2. Development Branch:

    • Create a new branch using Git on your local computer for this migration process. This branch will be where all initial commits are made, allowing us to keep the main branch clean and stable.
    • Use the following commands to create and switch to the development branch:
      git branch development
      git checkout development
      
  3. Committing Files:

    • Add your source code files to the staging area using git add . (This command adds all files except those listed in .gitignore).
    • Check with your instructor on whether the commit looks "ok" (do this before proceeding!)
    • Commit your changes with a meaningful message using git commit -m "Commit message".
    • Push your changes to GitHub using git push origin development.
  4. Create a Pull Request:

    • Happy with your development branch? Then create a pull request and merge it subsequently.

I migrated necessary folders from GoogleDrive.

I am reopening this issue because the data sets are not in our repositories. This needs to be fixed asap.

Thank you