-
-
Notifications
You must be signed in to change notification settings - Fork 437
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
Changed getOpenMageVersion()
#4496
base: main
Are you sure you want to change the base?
Conversation
$versionfromGit = self::getVersionFromGit($withHas); | ||
if ($versionfromGit) { | ||
return $versionfromGit; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't that collide with other repos that uses openMage?
if my repo has tags, then it would return my Repo tags instead of the OpenMage tags
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have two ways to install ...
- git clone ... gibt branch + hash is shown
- composer ... branch is shown
- having a fork with own tags ... your tag will be shown (you know what you have forked)
# Conflicts: # composer.lock
|
Tests work.
We dont need to upgrade the verion for every release anymore, but 3rd-party cant get the version info anymore.
In a composer-based procet you can detect the installed version easily. Do we need to have hardcoded version number?