Sorry, no merge conflicts.
Posting the new commit merged into
master rather than a pull request. Hopefully, that isn’t an issue.
Pull request with merge conflicts
In case it helps anybody, you can clone the repository to your computer then edit the file on Github to create a conflict. On your computer create a branch then edit the same file. When you do a pull request it will now see the conflict and ask you to resolve the issues. It helps when you type in text in the same location so it won’t be able to merge automatically. For example, change the name on github and on your local copy.
Hi @polbene95! It looks like this is a commit added to the repository, which is step one of what we’re looking for. This module is about collaboration, so if this is on a branch other than
master, please open a pull request and share a screenshot! If this commit is on your
master branch, please create a new branch, add a commit, and open a pull request.
@PReimers it looks like this is a commit on the master branch, not a pull request. Can you make a change via a PR for this module please? Thanks!
Sorry, the task didn’t mention anything about an other branch or a different remote.
I thought we should stick with the task notes.
Could you please tell me what I have to do exactly?
No you’re absolutely right @PReimers my mistake, I was making assumptions! You submission is fine!
I know that I am suppose to create a new branch and then create a new pull request, but let’s just say that I’ve forgot so, sorry about that.