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

Memote Git error #763

Open
parsanayyara opened this issue Apr 5, 2024 · 5 comments
Open

Memote Git error #763

parsanayyara opened this issue Apr 5, 2024 · 5 comments
Labels

Comments

@parsanayyara
Copy link

Hello,

I am trying to generate a memote report over a local git commit of a model and ran across this issue when trying to run

memote report history --location .

image

Followed the flowchart on https://memote.readthedocs.io/en/latest/flowchart.html but the error keeps showing up everytime I ran memote report. Could anyone help point out what the issue might be?

@carrascomj
Copy link
Member

It seems like your git repository does not contain the deployment branch "gh-pages". You can create it yourself with:

git checkout -b gh-pages

Did you start the repository with memote new or manually (git init)?

  • If you started it with memote new and still have this issue, could you paste your memote.ini here? There might be a bug with properly using the deployment branch.
  • If you started it with git init you may need other preparations for the repository that memote new performs (like generating a memote.ini and setting up the branches.)

Of course, if you only need a snapshot report, try:

memote report snapshot /path/to/model

@parsanayyara
Copy link
Author

Hello, I resolved the previous error, but now am getting a new one related to the cookiecutter.
image
image

It looks to me like it could not find the 'master' branch; might be because the recent Git update that changes master to main?

@carrascomj
Copy link
Member

Yes, that seems to be the problem, that must be fixed for it to work.

@carrascomj carrascomj added the bug label Apr 5, 2024
@parsanayyara
Copy link
Author

Is there any possible way around it that doesn't require modifying the code? Would it work if I rename main to master maybe?

@Midnighter
Copy link
Member

Is there any possible way around it that doesn't require modifying the code? Would it work if I rename main to master maybe?

We should change the cookiecutter to accept both master and main branches. Renaming the branch at this point won't help. You would have to manually perform the missing steps from the post generation hook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants