Skip to content

This is a project aimed at helping a freshers contribute to Hacktoberfest-2020 . Every A.C.M. member will have to Learn HTML,CSS,Bootstrap , javascript in order to contribute in this project .

Notifications You must be signed in to change notification settings

ACM-Thapar/Web-Portfolio

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

96 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Web-Portfolio

ACM-Thapar

GitHub issues Code style: black GitHub repo size

All Contributors


GitHub issues GitHub pull requests GitHub contributors

Project Description

This is a project aimed at helping a freshers contribute to Hactoberfest-2020 . Every ACM memeber will have to Learn HTML,CSS,Bootstrap,Js in oreder to contribute in this project . The learning resources are provided here . Each Member will have to make a web Portfolio of their own by following these instructions :-

We follow a systematic Git Workflow -

  • Create a fork of this repo.
  • Clone your fork of your repo on your pc.
  • Add Upstream to your clone
  • Every change that you do, it has to be on a branch. Commits on master would directly be closed.
  • You will start by creating a new folder by your name and put the entire code in that folder only . In the upcomming pr's just udate that code in that folder.
  • Create a new branch to fix a issue . Make required no. of commits .Make sure you write proper commit messages.
  • Push the branch to the origin tremote and make a pull request .
  • Make sure that before you create a new branch for new changes,syncing with upstream is neccesary.

Commit Guidelines

  • All commits are to be on a branch. Any on master will be closed
  • It is mandated that your branch is in sync with upstream, before you create a PR
  • If your PR is to fix an issue, make sure it contain's GitHub's keyword reference, which closes the related issue on PR merge
  • If changes are made to your PR, before merge(new commits to fix minor issues, like a failing Travis build), please squash your commits, so you don't have an absurd number of them
  • If your commit is for a UI change, it would be awesome if you add a screenshot, or a link to a deployment where it can be tested out, in your PR. Makes it easy to review and merge
  • Write clear, meaningful git commits
    • We recommend that changes be grouped locally with semantic prefixes to make it easier to understand, but not mandated. For example:

Pull Requests

Check out the pull request template here

About

This is a project aimed at helping a freshers contribute to Hacktoberfest-2020 . Every A.C.M. member will have to Learn HTML,CSS,Bootstrap , javascript in order to contribute in this project .

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published