Skip to content
This repository was archived by the owner on Aug 30, 2023. It is now read-only.

Conversation

@navdiya-nikunj
Copy link

screenshot of file:
Screenshot (7)

@navdiya-nikunj navdiya-nikunj changed the title Challange 5 navdiya-nikunj.md Challange 5 & 6 navdiya-nikunj.md Sep 6, 2022
@navdiya-nikunj navdiya-nikunj changed the title Challange 5 & 6 navdiya-nikunj.md Challange 5 & 6 & 7 navdiya-nikunj.md Sep 7, 2022
@navdiya-nikunj navdiya-nikunj force-pushed the navdiya-nikunj-details branch 2 times, most recently from a9804bd to 0b19608 Compare September 8, 2022 09:05
@navdiya-nikunj navdiya-nikunj changed the title Challange 5 & 6 & 7 navdiya-nikunj.md Challange 5 to 8 navdiya-nikunj.md Sep 8, 2022
@navdiya-nikunj navdiya-nikunj force-pushed the navdiya-nikunj-details branch 6 times, most recently from 6f47a44 to f1c287c Compare September 10, 2022 14:51
@navdiya-nikunj navdiya-nikunj changed the title Challange 5 to 8 navdiya-nikunj.md Challange (10/30) navdiya-nikunj Sep 10, 2022
@TeralaShivaKumar
Copy link

Hello navdiya-nikunj
Congratulations on successfully completing the milestone 1 of opensource challenge
and as promised you will receive your goodies soon and we appreciate your consistency

shivaylamba and others added 2 commits September 18, 2022 20:44
Update challenge_6.md squashed comits Create navdiya-nikunj.md Update navdiya-nikunj.md Create challenge_7.md Create challenge_7.md changed file location squashed comits Create navdiya-nikunj.md Update navdiya-nikunj.md Create challenge_7.md changed file location Revert "Merge branch 'navdiya-nikunj-details' of https://github.com/navdiya-nikunj/scaler-september-open-source-challenge into navdiya-nikunj-details" This reverts commit f33a094, reversing changes made to 671ebbb. Revert "Create challenge_7.md" This reverts commit 671ebbb. Revert "Update navdiya-nikunj.md" This reverts commit 8434fa2. Signed-off-by: Nikunj Navdiya <9723282128nnm@gmail.com>
Signed-off-by: Nikunj Navdiya <9723282128nnm@gmail.com>
@navdiya-nikunj navdiya-nikunj force-pushed the navdiya-nikunj-details branch 5 times, most recently from 7162b9d to 681a68a Compare September 18, 2022 16:08
Signed-off-by: Nikunj Navdiya <9723282128nnm@gmail.com>
Signed-off-by: Nikunj Navdiya <9723282128nnm@gmail.com>
@navdiya-nikunj navdiya-nikunj changed the title Challange (10/30) navdiya-nikunj Challange (19/30) navdiya-nikunj Sep 19, 2022
Signed-off-by: Nikunj Navdiya <9723282128nnm@gmail.com> Fixed linter errors Signed-off-by: Nikunj Navdiya <9723282128nnm@gmail.com> Solved linter error Signed-off-by: Nikunj Navdiya <9723282128nnm@gmail.com>
Signed-off-by: Nikunj Navdiya <9723282128nnm@gmail.com>
@navdiya-nikunj
Copy link
Author

Screenshot of website:-
Screenshot (52)

@navdiya-nikunj navdiya-nikunj changed the title Challange (19/30) navdiya-nikunj Challange (22/30) navdiya-nikunj Sep 22, 2022
@navdiya-nikunj
Copy link
Author

Chalange:- 23

Git Branching Naming Convention: Best Practices

Two categories of branch:-

  • Regular Git Branches
  • Temporary Git Branches
    - Bug Fix
    - Hot Fix
    - Feature Branches
    - Experimental Branches
    - WIP branches

    Git Branching Naming Convention

  1. Start branch name with a Group word
  2. Use Unique ID in branch names
  3. Use Hyphen or Slash as Separators
  4. Git Branch with Author Name
  5. Avoid using numbers only
  6. Avoid using all naming convention simultaneously
  7. Avoid long descriptive names for long-lived branches

Building a Great Pull Request

  • Give your feature branch a clear name
  • Give your commits and PRs active and descriptive titles
  • Streamline your process of creating a new PR
  • Give your PR a meaningful description
  • Show your functionality visually, whenever possible
  • Review your own PR before you assign it to others

FINDING AN ISSUE

Issues available for community contribution:

Following tags are used: -
help wanted: Open to participation from the community but not necessarily beginner-friendly
good first issue: Open to participation from the community and friendly towards new contributors

Issues not available for community contribution:

Following tags are used: -
staff only: Requires infrastructure access or institutional knowledge that would be impractical to provide to the community

Issues not ready for work:

Following tags are used: -
status: blocked: Blocked by other work that needs to be done first
status: ticket work required: Needs additional work before it is ready to be taken up
status: awaiting triage: Has not been triaged by a maintainer

Issues without any of the above labels:

These issues may (or may not) be open for contribution.
Please add a comment asking one of the maintainers to triage the issue and label it as appropriate.

@navdiya-nikunj navdiya-nikunj changed the title Challange (22/30) navdiya-nikunj Challange (23/30) navdiya-nikunj Sep 23, 2022
@kuraakhilesh8230
Copy link

Congratulations you have successfully completed milestone 2 and good to go 👏

@navdiya-nikunj navdiya-nikunj changed the title Challange (23/30) navdiya-nikunj Challange (27/30) navdiya-nikunj Sep 27, 2022
@navdiya-nikunj navdiya-nikunj changed the title Challange (27/30) navdiya-nikunj Challange (30/30) navdiya-nikunj Oct 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

4 participants