Skip to content

AndroidTechiesGTBIT/MajorCollegeProjectApp

Repository files navigation

Build Status

MajorProject - Android

This is an Android Application to display the details of the major projects of students in their final year(CSE, IT, ECE, EEE).

Setup for Developers

  1. Go to the project repo and fork it by clicking "Fork"
  2. If you are working on Windows, download Git Bash for Windows to get a full Unix bash with Git functionality
  3. Clone the repo to your desktop git clone https://github.com/YOUR_USERNAME/MajorCollegeProjectApp.git
  4. Open the project with Android Studio
  5. Fetch the latest version of code from branch "master".

Configure remotes

When a repository is cloned, it has a default remote called origin that points to your fork on GitHub, not the original repository it was forked from. To keep track of the original repository, you should add another remote named upstream:

  1. Set the upstream:

    git remote add upstream https://github.com/AndroidTechiesGTBIT/MajorCollegeProjectApp.git

  2. Run git remote -v to check the status, you should see something like the following:

origin https://github.com/YOUR_USERNAME/MajorCollegeProjectApp.git (fetch)

origin https://github.com/YOUR_USERNAME/MajorCollegeProjectApp.git (push)

upstream https://github.com/AndroidTechiesGTBIT/MajorCollegeProjectApp.git (fetch)

upstream https://github.com/AndroidTechiesGTBIT/MajorCollegeProjectApp.git (push)

  1. To update your local copy with remote changes, run the following:

    git fetch upstream

    git merge upstream/master

    This will give you an exact copy of the current remote, make sure you don't have any local changes.

Contributing and developing a feature

  1. Make sure you are in the master branch git checkout master
  2. Sync your copy git pull
  3. Create a new branch with a meaningful name git checkout -b branch_name
  4. Develop your feature on Android Studio and run it using the emulator or connecting your own Android device
  5. Clean your project from Android Studio Build/Clean project
  6. Add the files you changed git add file_name (avoid using git add .)
  7. Commit your changes git commit -m "Message briefly explaining the feature"
  8. Keep one commit per feature. If you forgot to add changes, you can edit the previous commit git commit --amend
  9. Push to your repo git push origin branch-name
  10. Go into the Github repo and create a pull request explaining your changes
  11. If you are requested to make changes, edit your commit using git commit --amend, push again and the pull request will edit automatically
  12. You will need to add a message on the pull request notifying your changes to your reviewer

Coding Guidelines

  1. Don't use magic numbers or hard-coded strings. Put them in dimens.xml or strings.xml
  2. Class names should be in CamelCase. Name activities with names including Activity so it's easier to know what they are.
  3. Include spaces between parameters when you call a method for example: Intent(MainActivity.this, GameActivity.class).
  4. Give relevant names to buttons and other resources.
  5. Use @id instead of @+id when referring to resources that have been already created in xml files.

Communication channels

  1. Slack group

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages