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

Inconsistency of the capitalization: Default vs default #3

Open
nskold opened this issue Mar 21, 2021 · 9 comments
Open

Inconsistency of the capitalization: Default vs default #3

nskold opened this issue Mar 21, 2021 · 9 comments

Comments

@nskold
Copy link
Owner

nskold commented Mar 21, 2021

Screenshot (62)
Screenshot (61)

Can someone please help me ?
I am a new person, having pushed from a TortoiseHg 5.7 client.

Thank you,
dloksnel@gmail.com

@Kotsuha
@10063987
@vitidev
@owenvoke
@sebunger
@philpep
@frescobaldi

@nskold
Copy link
Owner Author

nskold commented Mar 21, 2021

Screenshot (63)

@Kotsuha
Copy link

Kotsuha commented Mar 23, 2021

Hello. I do not fully understand your question. Do you want to push to GitHub but failed?

I guess you mentioned me because of this. Unfortunately I did not keep on with it. I encountered a problem (cannot recall what it is, maybe something about branch) and did not find solution. Everything I know about how to use TortoiseHg with GitHub is written in that repo. I know nothing more.

If TortoiseHg is giving you trouble pushing to GitHub, you may consider switching to Git. Yeah, not pleasing for Hg fans I know...

@vitidev
Copy link

vitidev commented Mar 23, 2021

I haven't used a github from TortoiseHg for a long time. Therefore, I will give only a few recommendations for hg-git.

  1. create repo -> clone -> modify -> push
  2. TortoiseHg has console panel with log.
  3. TorotiseHg support git refs as bookmarks (or local tags, I don't remember) and somethimes the tag not move when commit, and push do nothing without errors, so you have to move it manually.

@nskold
Copy link
Owner Author

nskold commented Mar 23, 2021

Hi Kotsuha,
Thank you for your kindness in commenting.
I have just one TortoiseHg repository, and about 6 subrepositories on this client.
I got "completed successfully" on the client side, for the push, but see none of my 70 files on the server side, that I hope is
github.com, and not bitbucket.org, about which I know nothing.
Is something missing from my local mercurial.ini file ?

Generated by TortoiseHg settings dialog

[tortoisehg]
maxdiff = <1900>
summarylen = 80
closeci = False
cipushafter = default-push
engmsg = False
refreshwdstatus = auto
confirmaddfiles = True
confirmdeletefiles = True

[mq]
secret = False

[phases]
new-commit = public
checksubrepos = follow

[ui]
username = nskold
askusername = False

Sincerely,
Art Lenskold
dloksnel@gmail.com

@nskold
Copy link
Owner Author

nskold commented Mar 24, 2021

Hi vitidev,
Your Recommendation #1 is a refreshing eye-opener for me.
I'll uninstall/ reinstall TortoiseHg with IObituninstaller, instead of trying to undo a local Commit.
To the TortoiseHg Settings I'll add hggit =.
I'll refrain from using the New Repository button.
I'll use the Clone Repository button, and experiment with the Add Subrepository button.
I'm hoping that the Clone of my only repository will accomplish the "handshake" between my local TortoiseHg client and the remote Github.com/nskold server once and for all.
So I'll need to think about renaming my new acutis1 repository that I set up manually on github.com, and to which I dragged and dropped the README.md, LICENSE, and .gitignore files.
Perhaps by adding the hggit = feature to my local mercurial.ini, via TortoiseHg Settings, the conflict between .gitignore and .hgignore may resolve itself, from what I gather from your Recommendation #3.

This new effort may take some time.
As a new person, I am unfamiliar with cloning.

Pertaining to this issue, I prefer the capitalized Default for use by the github.com server consistently, because the lower-case default seems to have a restricted meaning in at least the TortoiseHg client.

Thank you @Kotsuha and @vitidev for your valuable advice.

@vitidev
Copy link

vitidev commented Mar 24, 2021

hg-git won't be able to properly push the existing hg repository (to empty github repo) if it contains branches.

@nskold
Copy link
Owner Author

nskold commented Mar 24, 2021

Following @torbjoernk (2013), I'll try to avoid using mercurial subrepositories = "branches."
Thank you, @vitidev.
Art Lenskold
dloksnel@gmail.com

@nskold
Copy link
Owner Author

nskold commented Mar 25, 2021

I think I'll attempt to do the grunt work for my 70 files:
"... so you have to move it manually."

I have tried cloning, but TortoiseHg gives the message that it does not appear to be an hg repository.
There is a message partially in hexadecimal referencing github.githubassets.com.

@vitidev
Copy link

vitidev commented Mar 27, 2021

but TortoiseHg gives the message that it does not appear to be an hg repositor

This means that the hg-git extenison is not enabled

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

3 participants