mirrors/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2024-05-31 22:58:35 +00:00
Code Issues Projects Releases Wiki Activity

Merge branch 'origin/main' into 'next-release/main'

Browse source
This commit is contained in:
oauth 2024-05-06 07:21:58 +00:00
parent f0752cda90 f1b333628a
commit fe9013b558
2 changed files with 18 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
.woodpecker/social.yaml
View file

@ -6,7 +6,7 @@ when:
- event: tag
steps:
mastodon-toot:
- name: mastodon-toot
image: docker.io/woodpeckerci/plugin-mastodon-post
settings:
server: https://floss.social
@ -16,10 +16,18 @@ steps:
ai_token:
from_secret: openai_token
ai_prompt: |
We want to present the next version of our app on Twitter.
We want to present the next version of our app on Mastodon.
Therefore we want to post a catching text, so users will know why they should
update to the newest version. If there is no special feature included
just summarize the changes in a few sentences. Use #WoodpeckerCI, #release and
additional fitting hashtags and emojis to make the post more appealing.
update to the newest version. Highlight the most special features. If there is no special feature
included just summarize the changes in a few sentences. The whole text should not be longer than 240
characters. Avoid naming contributors from. Use #WoodpeckerCI, #release and
additional fitting hashtags and emojis to make the post more appealing
The changelog entry: {{ changelog }}
- name: discord
image: docker.io/appleboy/drone-discord:1.3.1
settings:
webhook_id: 1236558396820295711
webhook_token:
from_secret: discord_token
message: '**{{ build.tag }}** was released: <https://github.com/woodpecker-ci/woodpecker/releases/tag/{{ build.tag }}>'

6
docs/docs/20-usage/20-workflow-syntax.md
View file

@ -1,6 +1,10 @@
# Workflow syntax
The workflow section defines a list of steps to build, test and deploy your code. Steps are executed serially, in the order in which they are defined. If a step returns a non-zero exit code, the workflow and therefore all other workflows and the pipeline immediately aborts and returns a failure status.
The Workflow section defines a list of steps to build, test and deploy your code. The steps are executed serially in the order in which they are defined. If a step returns a non-zero exit code, the workflow and therefore the entire pipeline terminates immediately and returns an error status.
:::note
An exception to this rule are steps with a [`status: [failure]`](#status) condition, which ensures that they are executed in the case of a failed run.
:::
Example steps: