We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
app-id
The official Flatpak docs have the following in its list of "examples of bad IDs" on this page:
com.github.foo.Bar While a project may be hosted on GitHub it does not have any control over the github.com domain. Instead you should use io.github as shown above.
com.github.foo.Bar
While a project may be hosted on GitHub it does not have any control over the github.com domain. Instead you should use io.github as shown above.
github.com
io.github
The elementary packaging documentation gives the following instructions:
Create a com.github.yourusername.yourrepositoryname.yml file in your project root with the following contents:
com.github.yourusername.yourrepositoryname.yml
The elementary documentation recommends a practice which the Flatpak documentation explicitly lists as bad practice.
com.github
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The official Flatpak docs have the following in its list of "examples of bad IDs" on this page:
The elementary packaging documentation gives the following instructions:
The elementary documentation recommends a practice which the Flatpak documentation explicitly lists as bad practice.
Suggested solutions
io.github
instead ofcom.github
.com.github
isn't actually bad practice like it says in the Flatpak documentation.The text was updated successfully, but these errors were encountered: