Skip to content
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

fix(klassy): files #1138

Merged
merged 1 commit into from
Apr 30, 2024
Merged

fix(klassy): files #1138

merged 1 commit into from
Apr 30, 2024

Conversation

madonuko
Copy link
Member

No description provided.

Signed-off-by: madomado <[email protected]>
@madonuko madonuko enabled auto-merge (squash) April 30, 2024 06:56
@madonuko madonuko merged commit 6a1b812 into frawhide Apr 30, 2024
4 checks passed
@madonuko madonuko deleted the mado/fix/klassy branch April 30, 2024 12:10
@madonuko madonuko added bug Something isn't working sync-f38 sync-f40 labels Apr 30, 2024
@raboneko
Copy link
Member

💔 All backports failed

Status Branch Result
f38 Backport failed because of merge conflicts

You might need to backport the following PRs to f38:
- fix: espanso (#1126)
f39 Backport failed because of merge conflicts

You might need to backport the following PRs to f39:
- fix: espanso (#1126)
f40 An unhandled error occurred. Please see the logs for details

Manual backport

To create the backport manually run:

backport --pr 1138

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

raboneko pushed a commit that referenced this pull request Apr 30, 2024
Signed-off-by: madomado <[email protected]>
(cherry picked from commit 6a1b812)
raboneko pushed a commit that referenced this pull request Apr 30, 2024
Signed-off-by: madomado <[email protected]>
(cherry picked from commit 6a1b812)
@raboneko
Copy link
Member

💔 Some backports could not be created

Status Branch Result
f38 Backport failed because of merge conflicts

You might need to backport the following PRs to f38:
- fix: espanso (#1126)
f39 Backport failed because of merge conflicts

You might need to backport the following PRs to f39:
- fix: espanso (#1126)
f40

Manual backport

To create the backport manually run:

backport --pr 1138

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@raboneko
Copy link
Member

💔 Some backports could not be created

Status Branch Result
f38 Backport failed because of merge conflicts

You might need to backport the following PRs to f38:
- fix: espanso (#1126)
f39 Backport failed because of merge conflicts

You might need to backport the following PRs to f39:
- fix: espanso (#1126)
f40

Manual backport

To create the backport manually run:

backport --pr 1138

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

raboneko pushed a commit that referenced this pull request Apr 30, 2024
Signed-off-by: madomado <[email protected]>
(cherry picked from commit 6a1b812)
@raboneko
Copy link
Member

💔 Some backports could not be created

Status Branch Result
f38 Backport failed because of merge conflicts

You might need to backport the following PRs to f38:
- fix: espanso (#1126)
f39 Backport failed because of merge conflicts

You might need to backport the following PRs to f39:
- fix: espanso (#1126)
f40

Manual backport

To create the backport manually run:

backport --pr 1138

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working sync-f40
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants