Skip to content

Latest commit

 

History

History
24 lines (15 loc) · 2.43 KB

File metadata and controls

24 lines (15 loc) · 2.43 KB

Follow this instruction striclty

  • The applicaiton stlying is strict and follows the defined sets of design language only. do not edit any design or styling, i want that this application should look like how its now.

  • Strictly never use em dash (—), use simple dash, if any of the previous file have do not need to worry about that leave it as it, just do not use it in future.

  • This doc application very much foucsed on the in depth topics knowledeg/leaning and interview prep, so keep the thge notes like that only, it must be very much in depth so that nothing else is needed to know after that, (remember do not leave aything in the topic for later on), and also focused on easy language so that anyone can understand easily.

  • Any notes created must follow the sets of instructions and it must pass the defined test cases. do not edit test cases of our own till i have not approved or asked to for making anything work.

  • Never push the code to the main/master branch, crete a new branch or any code chnages it can like (codex/{feature-name}), name the PR using the PR naming conventions eg (feat, bug, chore, etc..). Once the branch is merge always take pull from the main/master and then create a new branch to work on.

  • Be very fundamental while doing any changes, think on it and then only do the chages, do not halucinate while working on any task.

  • Refer to TOPICS.md file as this file will contain the topics that are needed to be added in this docs application. This files will be frequently edited so always look for the fresh update, pick only at max 2 topics in one day, each topic will be a single PR, no PR will have more that one topic, every day look in the update of this codebase/project and do this in the loop till topics are finished.

Repository GitHub identity

  • Use the GitHub account shalshcode08 for this project.
  • Use the repository-local Git author name shalshcode08.
  • Use the repository-local Git author email somushrestha448@gmail.com.
  • Before pushing or creating a PR, verify that gh auth status shows shalshcode08 as the active authenticated account.
  • If authentication is missing or expired, run gh auth login --hostname github.com --git-protocol https --web and complete the GitHub login flow with the shalshcode08 account.
  • If several GitHub accounts are authenticated, run gh auth switch --hostname github.com --user shalshcode08 before publishing. Never store authentication tokens in this repository.