Skip to content

Updated MAIC201.md with the required changes. - #29

Open
Debatreya wants to merge 6 commits into
nkss-dev:mainfrom
Debatreya:main
Open

Updated MAIC201.md with the required changes.#29
Debatreya wants to merge 6 commits into
nkss-dev:mainfrom
Debatreya:main

Conversation

@Debatreya

Copy link
Copy Markdown

AI & ML -> AI

Specifics of Branch: PI -> removed

#Textbooks taken under #Reference Books

Debatreya and others added 5 commits November 6, 2023 21:02
AI & ML -> AI

Co-authored-by: Priyanshu Tripathi <priyanshutr@proton.me>
PI template removed

Co-authored-by: Priyanshu Tripathi <priyanshutr@proton.me>
@GetPsyched

GetPsyched commented Nov 7, 2023

Copy link
Copy Markdown
Contributor

Why open a new pull request and close the old one?

The new commits that you pushed showed up in the previous PR anyways.

@GetPsyched

Copy link
Copy Markdown
Contributor

Since I'm squashing the PR, these extra commits are not a problem. But it's generally a good idea to rebase instead of merging the default branch into your PR.

@Debatreya

Copy link
Copy Markdown
Author

Why open a new pull request and close the old one?

The new commits that you pushed showed up in the previous PR anyways.

Sir, actually I didn't knew that

@Debatreya

Copy link
Copy Markdown
Author

Since I'm squashing the PR, these extra commits are not a problem. But it's generally a good idea to rebase instead of merging the default branch into your PR.

Creating a new Branch?

@GetPsyched

Copy link
Copy Markdown
Contributor

No, rebasing is pushing your current branch (Debatreya:main in this case) on the tip of another branch (atlas:main in this case).

Check it up on documentation or videos, you'll find a lot of tutorials on what/how to rebase

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants