Review 2 Markdown preparation
bholebaba0135 opened this issue · comments
Guys, we'll be adding content for the review 2 to the Readme.md that already exists in this repository. No need to create a separate Markdown
- Make sure all commits are made to the beta branch. Will push everything to the main branch at the time of submission.
- Download Obsidian if you haven't installed it yet as well as Zotero. Install both the chrome extension as well as the PC software.
- Lets have a meet this evening. I am informing the same on WhatsApp group. However all communication henceforth would be via issues as it is part of the rubrics for review 2
3 important things to note to make sure that the process of collaboration is smooth sailing:
- Everyday commit and push your work to the beta in the self chosen time interval which has already been decided.
- Run a git pull command everytime you start working on the markdown in your local obsidian vault. This is to make sure that you are always working in sync with latest version of the beta branch
- Workflow has been added. Kindly check the Readme.md. There's a backlink in the Roles and Responsibilities section. Comment here for any doubts
Downloaded Obsidian and zotero
if someone had pushed the changes in beta and then those have been pushed in main, then we need to pull those again or it will get updated automatically in our local git?
Have added the literature survey table format, will soon work on the papers.
@prakhargoyal3043 if you are creating a branch from main then all the commits in the main at the point of the creation of branch would also be copied in branch but later any changes in main wont reflect in other branches. It would show that main is x commits ahead of your branch.
For now just ignore if you receive such notifications. I'll push the content from every contributor's branch before going for review 2
Also by local git if you meant the local repository on your PC then make sure of 2 things:
- You should always be present on your own branch and not on any other branch. To navigate to your own branch enter command 'git checkout Prakhar'
- It is generaly advised to run a 'git pull' command each time you git bash since many people are collaborating but since you are the only one commiting to your branch from your local repo, its not necessary.
I am getting this error when i am trying to push.
@harshitub2 This error indicates that ur local version of the repo is not updated to the latest changes in our remote repo on github. Git gives this error to prevent overwriting of one collaborator's changes by another collaborator.
To resolve this, just make sure you enter the command 'git pull' everytime you start working. After that you can add your changes, commit them and push to the remote repo.
I have added the research papers and pushed those.
Added the research papers and pushed them.
Literature Survey is done guys
We have to change little bit more for more perfection.
all the literature surveys added and pushed in my branch
all the literature surveys added and pushed in my branch
What about the Methodologies
Literature Survey is done
Methodologies done
i Also completed the survey part,Any updates on methodologies?
I'm trying to push my code to the GitHub repo, but it showing that my git push is rejected. why?
write down all the methodologies after the survey part and push it.
all the literature surveys added and pushed in my branch
What about the Methodologies
@Vivekrathore2002 You can push them to your branch. I will merge it into main after reviewing
Make sure you run the git pull command first in your git bash
Then, Add the Methodologies section below Literature Surveys in the following format
Methodologies
- Paper title:
(Methodology content)
then git add, commit and push
okay
@pranjal6314 once check
I'm trying to push my code to the GitHub repo, but it showing that my git push is rejected. why?
once try again with correct folder
I'm trying to push my code to the GitHub repo, but it showing that my git push is rejected. why?
Did you try git pull before making the changes?
@Vivekrathore2002 first do pull request because there is many changes on github repo
use git pull
@Vivekrathore2002 first do pull request because there is many changes on github repo use git pull
Sure i will take care of that
@everyone, click on contribute -> open pull request from your own branch if you are done adding methodology. I will merge it then. Dont merge yourself
done
wait for some time then run "git pull" then do git push
okay I will try it
first check your all are in your own branch then push
okay done
