dwm picom added

This commit is contained in:
wt committed 2024-08-08 16:59:22 +07:00
1 parent 471b6062af
commit 964ff4b2c7
132 files changed
+32922

No files matched your search

+57
View File
@@ -0,0 +1,57 @@
<!-- The template below is for reporting bugs. For feature requests and others, feel free to delete irrelevant entries. -->
### Platform
<!-- Example: Ubuntu Desktop 17.04 amd64 -->
### GPU, drivers, and screen setup
<!--
Example: NVidia GTX 670, nvidia-drivers 381.09, two monitors configured side-by-side with xrandr
Please include the version of the video drivers (xf86-video-*) and mesa.
Please also paste the output of `glxinfo -B` here.
-->
### Environment
<!-- Tell us something about the desktop environment you are using, for example: i3-gaps, Gnome Shell, etc. -->
### picom version
<!-- Put the output of `picom --version` here. -->
<!-- Example: v8.2 -->
<details>
<summary>Diagnostics</summary>
<!-- Please also include the output of `picom --diagnostics` -->
</details>
### Configuration:
<details>
<summary>Configuration file</summary>
```
// Paste your configuration here
```
</details>
### Steps of reproduction
<!--
If you can reliably reproduce this bug, please describe the quickest way to do so
This information will greatly help us diagnosing and fixing the issue.
-->
1.
2.
### Expected behavior
### Current Behavior
### Stack trace
<!--
If the compositor crashes, please make sure you built it with debug info, and provide a stack trace captured when it crashed.
Note, when the compositor crashes in a debugger, your screen might look frozen. But gdb will likely still handle your input if it is focused.
Often you can use 'bt' and press enter to get the stack trace, then 'q', enter, 'y', enter to quit gdb.
-->
<!-- Or, you can enable core dump, and upload the core file with the corresponding executable here. -->
### Other details
<!-- If your problem is visual, you are encouraged to record a short video when the problem occurs and link to it here. -->
+1
View File
@@ -0,0 +1 @@
<!-- Please enable "Allow edits from maintainers" so we can make necessary changes to your PR -->
+47
View File
@@ -0,0 +1,47 @@
name: "CodeQL"
on:
push:
branches: [next]
pull_request:
branches: [next]
jobs:
analyze:
name: Analyze
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
language: ['cpp', 'python']
steps:
- name: Checkout repository
uses: actions/checkout@v2
with:
# We must fetch at least the immediate parents so that if this is
# a pull request then we can checkout the head.
fetch-depth: 2
# If this run was triggered by a pull request event, then checkout
# the head of the pull request instead of the merge commit.
- run: git checkout HEAD^2
if: ${{ github.event_name == 'pull_request' }}
# Initializes the CodeQL tools for scanning.
- name: Initialize CodeQL
uses: github/codeql-action/init@v1
with:
languages: ${{ matrix.language }}
# Install dependencies
- run: sudo apt update && sudo apt install libxext-dev libxcb1-dev libxcb-damage0-dev libxcb-xfixes0-dev libxcb-shape0-dev libxcb-render-util0-dev libxcb-render0-dev libxcb-randr0-dev libxcb-composite0-dev libxcb-image0-dev libxcb-present-dev libxcb-xinerama0-dev libxcb-glx0-dev libpixman-1-dev libdbus-1-dev libconfig-dev libgl1-mesa-dev libpcre2-dev libevdev-dev uthash-dev libev-dev libx11-xcb-dev meson ninja-build
if: ${{ matrix.language == 'cpp' }}
# Autobuild
- name: Autobuild
uses: github/codeql-action/autobuild@v1
- name: Perform CodeQL Analysis
uses: github/codeql-action/analyze@v1
+13
View File
@@ -0,0 +1,13 @@
name: coding-style
on: pull_request
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- run: git fetch --depth=1 origin ${{ github.event.pull_request.base.sha }}
- uses: yshui/git-clang-format-lint@v1.11
with:
base: ${{ github.event.pull_request.base.sha }}
+14
View File
@@ -0,0 +1,14 @@
name: coding-style
on: push
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
with:
fetch-depth: 2
- uses: yshui/git-clang-format-lint@v1.12
with:
base: ${{ github.event.ref }}~1