aws / aws/amazon-sagemaker-examples

[Known issue] Your configuration specifies to merge with the ref 'refs/heads/master' from the remote, but no such ref was fetched

Open
#3,132 9 comments 60 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
11k
Forks
7k
Avg merge
8h 29m
Merged PRs (30d)
8

Description

This message occurs now that the default branch has been renamed to "main", but your clone is still attempting to pull from "master".

To resolve this issue, run the following CLI commands in your local cloned repository:

```
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
```

This will allow you to continue to pull the latest commits as usual.

Please refer to the announcement: https://github.com/aws/amazon-sagemaker-examples/discussions/3131

Contributor guide

Open the contributing guide

Research direction

Start with the migration announcement in GitHub discussion #3131 and reproduce the reported message in a clone whose upstream still targets master. Verify the documented branch and remote commands, with completion shown by successful pulls from origin/main; no project file or test is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
tooling
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.