-
-
Notifications
You must be signed in to change notification settings - Fork 451
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
Add support for Suse Linux #624
Conversation
Version 4.0.0
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.
Can you add Suse to metadata.json?
I see unrelated changes, maybe due to the merge commits?
You can probably fix this by rebasing and squashing your commits:
From your working directory:
git fetch origin # Download the latest code we have here
git rebase origin/master # Move your commits on top of the main branch
git rebase -i origin/master # Interactively rewrite history
This will bring your editor. Keep the first line unchanged, and replace pick
with squash
for all subsequent lines. Save and quit, your editor will allow you to combine the commit messages in a single commit message.
Then push your updated branch to update the Pull-Request:
git push -f # Send the changes (-f is required because we re-wrote history)
Hi @fbrehm , can you take a look at the above comments? |
…eclaring it for private.
Update metadata.json - lower version boundary Co-authored-by: Tim Meusel <[email protected]>
Pull Request (PR) description
This Pull Request (PR) fixes the following issues