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

GitHub branch configuration #51

Open
1 of 2 tasks
GitMensch opened this issue Jul 11, 2022 · 6 comments
Open
1 of 2 tasks

GitHub branch configuration #51

GitMensch opened this issue Jul 11, 2022 · 6 comments

Comments

@GitMensch
Copy link
Collaborator

GitMensch commented Jul 11, 2022

I suggest to do the following:

@nberth
Copy link
Contributor

nberth commented Jul 11, 2022

I agree the purpose of this repository is mainly about branch gcos4gnucobol-3.x.
@lefessan do you think protecting branches master and gnucobol-3.x would break your mechanics for importing upstream branches?

@GitMensch
Copy link
Collaborator Author

@lefessan do you think protecting branches master and gnucobol-3.x would break your mechanics for importing upstream branches?

Just a friendly ping @lefessan; whatever your answer is, I think we can close this issue afterwards (while this still brings in the question about switching to the gnucobol3 repo instead; we can definitely drop gnucobol2 already).

@lefessan
Copy link
Member

Unfortunately, I don't think I can protect the branches as the sync process pushes directly into these branches.

I am going to push a base branch (maybe with another name than gcos4gnucobol) with the git-related commits.

@GitMensch
Copy link
Collaborator Author

GitMensch commented Mar 17, 2023

Would it be useful for the gnucobol3 repo to re-import (if not possible otherwise) with enabled committer translation? Just have a look the history nberth committing is not nberth :-)

@lefessan
Copy link
Member

It's a bit weird, I didn't do anything different from the previous gnucobol repo, committer translation was better done the first time. Ok, I will need to investigate what changed and how it can be fixed...

@GitMensch
Copy link
Collaborator Author

Ping @lefessan the current mirroring seem to not translate (any more?)
Neither sf-mensch nor ddeclerck are transformed in the git branches

Note: if you haven't the translation from "chaat" to @chuck-haatvedt you may want to add it.

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