-
Notifications
You must be signed in to change notification settings - Fork 34
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
Include metafacture-fix #577
Comments
Status update: I've successfully performed the outlined steps towards a potential merge (as of metafacture/metafacture-fix@b254549). This was initially meant as a dry-run, but seeing as it wasn't always straightforward along the way1, I'd very much like to be able to use my current state for the actual merge (pull request). The only thing holding us back (AFAICS) is the pending release. Can we agree on freezing all activity in the metafacture-fix repository right now? Meaning: No new commits and pull requests! Ideally, no new issues either. The release process itself doesn't matter since the version number and tags aren't carried over anyway. Footnotes
|
Modifications made while importing metafacture/metafacture-fix@b254549 (see 1784fda): Modified files:
Deleted files and directories:
|
Merge metafacture-fix repository to ease maintenance and support burden as well as simplify development and use. See metafacture/metafacture-fix#298 for previous discussion.
Preconditions:
Course of action:
--no-tags
).--allow-unrelated-histories
).README.md
,build.gradle
, etc.), preserve current subprojects (metafix*
) and namespace (org.metafacture.metafix
).metafacture-runner
.External users? (@hagbeck, @UBmakla, ...)Post-migration steps:
README.md
and description to point to new repository.Cleanup:
metafix-runner
(already done during merge)..gitignore
file (remove obsolete patterns, structure metafacture-fix patterns).toolVersion
).checkstyleTest.enabled
).StaticVariableName
).MissingJavadocMethod
).metafix
integration tests only when necessary (would otherwise slow down all workflows, including pull request checks).The text was updated successfully, but these errors were encountered: