forgejo/docs
32
45
Fork
You've already forked docs
204

fix actions conditionals with missing quotes #1023

Merged
earl-warren merged 1 commit from mahlzahn/fix_actions_conditional_missing_quotes into next 2025年01月13日 14:42:43 +01:00 AGit

This fixes

  • again the links.yml, which was not updating issue #583 anymore
  • the concerning documentation of actions:
- if: !cancelled()
+ if: '!cancelled()'

(Solution found here)

This fixes - again the links.yml, which was not updating issue #583 anymore - the concerning documentation of actions: ```diff - if: !cancelled() + if: '!cancelled()' ``` (Solution found [here](https://stackoverflow.com/a/58859404))
mahlzahn force-pushed mahlzahn/fix_actions_conditional_missing_quotes from d39e2ac2e8
All checks were successful
pr / preview (pull_request_target) Successful in 2m1s
to f338c137df
All checks were successful
pr / preview (pull_request_target) Successful in 1m39s
backport / backport (pull_request_target) Has been skipped
2025年01月13日 10:19:06 +01:00
Compare
Collaborator
Copy link
Preview ready: https://forgejo.codeberg.page/@docs_pull_1023/docs/next/user/actions/#conditionals
mahlzahn force-pushed mahlzahn/fix_actions_conditional_missing_quotes from f338c137df
All checks were successful
pr / preview (pull_request_target) Successful in 1m39s
backport / backport (pull_request_target) Has been skipped
to fcb5cb5634
All checks were successful
pr / preview (pull_request_target) Successful in 1m20s
backport / backport (pull_request_target) Successful in 5s
2025年01月13日 10:50:52 +01:00
Compare
Author
Member
Copy link
Btw, I put some test workflows here: https://code.forgejo.org/mahlzahn/forgejo-actions-test/src/branch/main/.forgejo/workflows Maybe, they or parts of them could be integrated into https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions ?
earl-warren left a comment
Contributor
Copy link

I was bitten more than once by this rather non-intuitive YAML thing 👍

I was bitten more than once by this rather non-intuitive YAML thing 👍
Collaborator
Copy link

The backport to v10.0 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v10.0 v10.0
# Navigate to the new working tree
cd .worktrees/backport-v10.0
# Create a new branch
git switch --create backport/v10.0/pr-1023
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 900cbfd759cda0efe93f49d0f07e5525152ac8a6
# Push it to GitHub
git push --set-upstream origin backport/v10.0/pr-1023
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v10.0

Then, create a pull request where the base branch is v10.0 and the compare/head branch is backport/v10.0/pr-1023.

The backport to `v10.0` failed: ``` The process '/usr/bin/git' failed with exit code 1 ``` To backport manually, run these commands in your terminal: ```bash # Fetch latest updates from GitHub git fetch # Create a new working tree git worktree add .worktrees/backport-v10.0 v10.0 # Navigate to the new working tree cd .worktrees/backport-v10.0 # Create a new branch git switch --create backport/v10.0/pr-1023 # Cherry-pick the merged commit of this pull request and resolve the conflicts git cherry-pick -x --mainline 1 900cbfd759cda0efe93f49d0f07e5525152ac8a6 # Push it to GitHub git push --set-upstream origin backport/v10.0/pr-1023 # Go back to the original working tree cd ../.. # Delete the working tree git worktree remove .worktrees/backport-v10.0 ``` Then, create a pull request where the `base` branch is `v10.0` and the `compare`/`head` branch is `backport/v10.0/pr-1023`.
Contributor
Copy link

Btw, I put some test workflows here: https://code.forgejo.org/mahlzahn/forgejo-actions-test/src/branch/main/.forgejo/workflows

Maybe, they or parts of them could be integrated into https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions ?

That sounds like a great idea. There are a few but not enough.

> Btw, I put some test workflows here: https://code.forgejo.org/mahlzahn/forgejo-actions-test/src/branch/main/.forgejo/workflows > > Maybe, they or parts of them could be integrated into https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions ? That sounds like a great idea. There are [a few](https://code.forgejo.org/forgejo/end-to-end/src/branch/main/actions/example-if-fail) but not enough.
Author
Member
Copy link

Finally, it worked. Now, the number of dead links is reduced by one half :)

Finally, it worked. Now, the number of dead links is reduced by one half :)
Contributor
Copy link

Yeah!

Yeah!
Sign in to join this conversation.
No reviewers
Labels
Clear labels
404

Broken links or missing content
backport/v1.19

Changes which should be backported to the v1.19 docs

Archived

backport/v1.20

Changes which should be backported to the v1.20 docs

Archived

backport/v1.21

Changes which should be backported to the v1.21 docs

Archived

backport/v10.0

Automated backport to v10.0

Archived

backport/v11.0

Automated backport to v11.0
backport/v12.0

Automated backport to v12.0

Archived

backport/v13.0

Automated backport to v13.0
backport/v14.0

Automated backport to v14.0
backport/v7.0

Automated backport to the v7.0 docs

Archived

backport/v8.0

Automated backport to the v8.0 docs

Archived

backport/v9.0

Automated backport to the v9.0 docs

Archived

good first issue

This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
meta

Tooling and processes for maintaining the docs
new docs

Content to be added to the documentation

Archived

User research - Accessibility

Requires input about accessibility features, likely involves user testing.
User research - Blocked

Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community

Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)

Instance-wide configuration, authentication and other admin-only needs.
User research - Errors

How to deal with errors in the application and write helpful error messages.
User research - Filters

How filter and search is being worked with.
User research - Future backlog

The issue might be inspiring for future design work.
User research - Git workflow

AGit, fork-based and new Git workflow, PR creation etc
User research - Labels

Active research about Labels
User research - Moderation

Moderation Featuers for Admins are undergoing active User Research
User research - Needs input

Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard

Research on how users should know what to do next.
User research - Rendering

Text rendering, markup languages etc
User research - Repo creation

Active research about the New Repo dialog.
User research - Repo units

The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)

How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/docs!1023
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "mahlzahn/fix_actions_conditional_missing_quotes"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?