best/safest practice for interacting with github

[Steve Fink]

On Mon, Nov 18, 2019 at 1:32 PM Ernie Rael <err at raelity.com> wrote:
>
> You use netbeans.git, I don't have the ".git" extension. Is there some
> magic, or is it a naming convention?

I think that's magic on the github side. I believe the URL will go to
the same place with or without the .git.

> The example has 'hg push -r mybranch', why not '... -B mybranch'? I
> guess they're equivalent in this case.

I think the only difference would normally be that -B would push the
bookmark metadata itself, but it seems like even `hg push -r .`
informs the git server of the active bookmark name, so they seem
equivalent?

>
> When you say
>
>     hg-git [has issues so] ... don't rewrite ... changes you've already
>     pushed
>
> I think of pushing a change, then needing to revise it after review and
> wanting to 'hg squash'. Should I wait till (not if, when) that happens?
> Are there things I can do beforehand to minimize potential problems? Or
> maybe some light reading so those workarounds don't come as a total shock:-)

Kevin will have to answer that. I *thought* I had been fine pushing
updated changesets to a github pull request, and having it replace the
originals a la git push -f. I can certainly imagine problems once the
PR has been merged into master. You will need to use -f to push the
updates, same as with git. I just tried a very basic test, and it
worked ok. (It was just one change on a new bookmark, amended and
force-pushed after creating a PR.)