1d4f01e...master · flathub

git.iko.soy/flathub

6 files changed+90−14

since splitsnapshots

unifiedsplit

.github/pull_request_template.md+13 .github/workflows/external-data-checker.yml+12 .github/workflows/merge.yml+16 .github/workflows/stale.yml+15 CONTRIBUTING.md+15 README.md+19−14

.github/pull_request_template.mdnew file+13

@@ -0,0 +1,13 @@

1+### Please confirm your submission meets all the criteria

3+- [ ] I have read the [App Requirements][reqs] and [App Maintenance][maint] pages.

4+- [ ] My pull request follows the instructions at [App Submission][submission].

5+- [ ] I am using only the minimal set of permissions. *(If not, please explain each non-standard permission.)*

6+- [ ] All assets referenced in the manifest are redistributable by any party. If not, the unredistributable parts are using an extra-data source type.

7+- [ ] I am an upstream contributor to the project. If not, I contacted upstream developers about submitting their software to Flathub. **Link:**

8+- [ ] I own the domain used in the application ID or the domain has a policy for delegating subdomains (e.g. GitHub, SourceForge).

9+- [ ] Any additional patches or files have been submitted to the upstream projects concerned. *(If not, explain why.)*

10+

11+[reqs]: https://github.com/flathub/flathub/wiki/App-Requirements

12+[maint]: https://github.com/flathub/flathub/wiki/App-Maintenance

13+[submission]: https://github.com/flathub/flathub/wiki/App-Submission

.github/workflows/external-data-checker.ymlnew file+12

@@ -0,0 +1,12 @@

1+name: 'Check if external data changed across Flathub org'

2+on:

3+ schedule:

4+ - cron: '0 * * * *'

6+jobs:

7+ flathub-data-checker-global:

8+ runs-on: ubuntu-latest

9+ steps:

10+ - uses: flathub/actions/flathub-external-data-checker@master

11+ env:

12+ GITHUB_TOKEN: ${{ secrets.FLATHUBBOT_TOKEN }}

.github/workflows/merge.ymlnew file+16

@@ -0,0 +1,16 @@

1+name: Automatic application merge

3+on:

4+ issue_comment:

5+ types:

6+ - created

8+jobs:

9+ merge:

10+ runs-on: ubuntu-latest

11+ container:

12+ image: ghcr.io/flathub/actions/merge:latest

13+ steps:

14+ - run: /entrypoint.py

15+ env:

16+ GITHUB_TOKEN: ${{ secrets.FLATHUBBOT_TOKEN }}

.github/workflows/stale.ymlnew file+15

@@ -0,0 +1,15 @@

1+name: "Close stale PR"

2+on:

3+ schedule:

4+ - cron: "0 0 * * *"

6+jobs:

7+ stale:

8+ runs-on: ubuntu-latest

9+ steps:

10+ - uses: actions/stale@v1

11+ with:

12+ repo-token: ${{ secrets.FLATHUBBOT_TOKEN }}

13+ stale-pr-message: "This PR hasn't received any updates in a year and will be automatically closed in 14 days. Feel free to re-open it if you plan to continue working on that pull request or think it deserves attention from Flathub admins"

14+ days-before-stale: 365

15+ days-before-close: 14

CONTRIBUTING.mdnew file+15

@@ -0,0 +1,15 @@

1+### Submitting a new package

3+If you are submitting a new package please read the [app submission](https://github.com/flathub/flathub/wiki/App-Submission) and [app requirements](https://github.com/flathub/flathub/wiki/App-Requirements) pages in the wiki.

5+Also double-check that your PR is against the `new-pr` branch.

7+### Reporting a bug on a package

9+Please open bugs for packages on their respective repositories you can search for them here: https://github.com/flathub

10+

11+### Requesting a new package

12+

13+Please do not open issues requesting packages. As long as a package meets the guidelines above and works it will be

14+generally be accepted. If you want to create a Flatpak see the [documentation](https://flatpak.readthedocs.io/en/latest/)

15+or join [#flatpak:matrix.org](https://matrix.to/#/#flatpak:matrix.org) for help.

README.md+19−14

@@ -1,22 +1,27 @@

1−This is where the magic happens.

1+# Flathub

3−Application manifests should go in their own branches, named after the application ID.

3+Flathub is the central place for building and hosting Flatpak builds.

5−For example, for gnome-recipes, there is a branch named org.gnome.Recipes which has

6−the org.gnome.Recipes.json file at the toplevel.

5+Using the Flathub repository

6+----------------------------

8−The manifests should build releases, not development snapshots, so please use

9−tarballs or git tags, not just the tip of a branch.

8+To install applications that are hosted on Flathub, use the following:

9+```

10+flatpak remote-add flathub https://flathub.org/repo/flathub.flatpakrepo

11+flatpak install flathub org.gnome.Recipes

12+```

1013

11−In case you build from a git tag, please specify both the tag name and the commit id, liks so:

14+To install applications from the beta branch, use the following:

1215```

13− "branch": "1.0.4",

14− "commit": "cdfb19b90587bc0c44404fae30c139f9ec1cca5c"

16+flatpak remote-add flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo

17+flatpak install flathub-beta org.godotengine.Godot

1518```

16−This makes the build repeatable, since a tag can otherwise change its value over time.

17−You can also use only a commit, but specifing a tag name if there is one is good for readability.

1819

19−Flathub always builds in the flatpak branchname "stable", and it always passes --default-name=stable,

20−so you don't need to specify a branch key. But if you do (not recommended), it must be "stable".

20+For more information and more applications see https://flathub.org

21+

22+Contributing to Flathub

23+-----------------------

24+

25+For information on creating packages or reporting issues please see the [contributing page](/CONTRIBUTING.md).

2126

22−All applications in flathub should ship with appstream data.

27+***Note:*** *this repository is not for reporting issues related to the flathub.org website itself or contributing to its development. For that, go to https://github.com/flathub/website*