Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

So, you’ve decided to change your r package name | Credibly Curious #65

Open
utterances-bot opened this issue Jan 23, 2022 · 8 comments

Comments

@utterances-bot
Copy link

So, you’ve decided to change your r package name | Credibly Curious

https://www.njtierney.com/post/2017/10/27/change-pkg-name/

Copy link

After I have done that, the following things are happening:

  • "git status" outputs
    On branch main
    nothing to commit, working tree clean
    instead of
    On branch main
    Your branch is up to date with 'origin/main'.
    nothing to commit, working tree clean
  • "git branch -a" shows only "main", and none of the remote branches.

Please, what can I do to have this fixed?

@njtierney
Copy link
Collaborator

Hi there!

Here's a couple of thoughts - hopefully these are helpful:

You could show your current remotes with:

git remote -v

If you don't have any remotes, you can add them?

# set the new URL
git remote set-url origin <YOUR REPO URL>
# check the remote
git remote -v 

I think that should help?

Copy link

Thank you very much, njtierney.

Actually, git remote -v shows the remotes for fetch and push.

But I could solve the problem by cloning the repo in another folder with git clone MY_REPO_URL. I hope this doesn't get me any problem in the future.

Copy link

This was really helpful. Thanks a lot!

Copy link

Thanks for sharing this information. This was really helpful in changing my package name.

Copy link

This is a blog I come back to time and time again! Thank you Nick :)

Copy link

For those who read, an error I ran into was to change the name of the package in the .Rbuildignore file

Thank you for the helpful post!

Copy link

Great post. can be follow safely. no problem.

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

No branches or pull requests

8 participants