summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2024-05-08removed unneeded build scripts and workflowsWilliam McKinnon
2024-04-29removed old publish script, updated to 0.4William McKinnon
2023-12-03Fixed AUR Github Action not including sway-portals.conf (#247)Erik Reider
* Added sway-portals.conf to AUR publish Action * Bumped PKGBUILD pkgrel
2023-03-10ver: bump to 0.2 (#87)Erik Reider
Co-authored-by: Erik Reider <[email protected]>
2022-11-18Improved copr install testing (#55)Erik Reider
2022-11-15AUR publish actions: Remove checkingout of tag (#42)Erik Reider
2022-11-14Updated build scriptsErik Reider
Co-authored-by: Erik Reider <[email protected]>
2022-11-13Add PKGBUILD stable and -git, AUR publish and Arch build GitHub Actions (#31)Erik Reider
* Create AUR_publish.yml * Added PKGBUILD * Switched AUR publish addon * Added arch-build action * Remove useless step in arch-build * Checkout latest tag instead of master for Arch and Fedora publish actions * Added -git PKGBUILD and added wlroots < 0.16 as dependency * Checkout master before running swayfx-git aur script * Check build for stable PKGBUILD after -git version * Removed spaces in wlroots depends version
2022-11-04Added GitHub build and copr actionsErik Reider
2022-08-16updated issue templateWill McKinnon
2021-10-17github: don't truncate debug logsSimon Ser
This happens a lot, the latest one is [1]. [1]: https://github.com/swaywm/sway/issues/6570
2021-05-26Fix IRC links in READMEs and templatesapt-ghetto
Change the webchat links from freenode.net to point to the new destination libera.chat. Co-authored-by: Simon Ser <[email protected]>
2021-03-30Remove advice about Firefox from issue templateSimon Ser
Firefox got a lot better. I think now would be a good time to remove the advice from the issue template. We can always add it back if we start getting invalid bug reports again.
2021-01-26Fix typo in bug reporting templateMartin Michlmayr
2021-01-04Remove call for action from WM enhancement issue templateSimon Ser
i3 feature set is mostly frozen as well, so we shouldn't advise people to open feature requests there. Moreover, i3 will disregard feature requests from sway users (because it doesn't benefit the i3 project itself). There is now no good way to request new WM features, and this is by design. This aligns with [1]. [1]: https://github.com/swaywm/sway/commit/fc1148da7f9c7bfc81f29e2b8304ae4e1592d95d
2020-12-26Remove .github/FUNDING.ymlDrew DeVault
Since I'm no longer a maintainer of, or regular contributor to, this project, it doesn't make sense to solicit donations.
2020-12-18ISSUE_TEMPLATE: the wiki is community maintainedRouven Czerwinski
Mention that the github wiki may contain outdated information scripts and old workarounds and that sway the sway project does not provide support for it.
2020-07-06ISSUE_TEMPLATE: Use the newer issue templatesBrian Ashworth
This utilizes the newer Github issue templates. They allow for the user to specify what type of issue they are submitting to allow for a more specific issue template to be shown. In addition to a hopefully easier to read/parse/follow bug report template, this also include templates for enhancements and i3 compatibility. This also includes a link to the IRC under the section title Questions. For the three templates, the labels bug, enhancement, and i3-compat will be automatically applied for the appropriate report to assist in triaging. Hopefully, this will result in less questions and issues for new window management functionality on Github and allow for better quality issues being submitted. At the very least, it allows us to outline our stances for bugs, enhancements, and i3-compatibility in an easier to read format.
2019-10-11Update .github/FUNDING.ymlDrew DeVault
2019-05-25Create FUNDING.ymlDrew DeVault