-
Notifications
You must be signed in to change notification settings - Fork 0
59 lines (54 loc) · 2.52 KB
/
dartdoc.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
name: dart-doc-generation
run-name: "docs(doc): generate dart documentation from code comments"
on:
push:
branches:
- 11-documentation-documentation-generation-and-publishing
- dev
- main
paths:
- revoiceme/lib/**
jobs:
dart-doc-generation:
runs-on: ubuntu-latest
steps:
# use public action to checkout the repository
- name: checkout repository
- uses: actions/checkout@v4
# install flutter
- name: install flutter
- run: sudo snap install flutter --classic
# change to
- name: run documentation generator
- run: ls
- run: cd revoiceme
- run: dart doc
# stages changes, commits them and pushs them as contributor "github_actor"
- name: commit and push
- uses: EndBug/add-and-commit@v9 # You can change this to use a specific version.
with:
# The arguments for the `git add` command (see the paragraph below for more info)
# Default: '.'
add: 'src'
# Additional arguments for the git commit command. The --message argument is already set by the message input.
# Default: ''
commit: --signoff
# Determines the way the action fills missing author name and email. Three options are available:
# - github_actor -> UserName <[email protected]>
# - user_info -> Your Display Name <[email protected]>
# - github_actions -> github-actions <email associated with the github logo>
# Default: github_actor
default_author: github_actor
# Arguments for the git fetch command. If set to false, the action won't fetch the repo.
# For more info as to why fetching is usually recommended, please see the "Performance on large repos" FAQ.
# Default: --tags --force
fetch: false
# The message for the commit.
# Default: 'Commit from GitHub Actions (name of the workflow)'
message: 'docs(doc): generate dart documentation from code comments'
# The way the action should handle pathspec errors from the add and remove commands. Three options are available:
# - ignore -> errors will be logged but the step won't fail
# - exitImmediately -> the action will stop right away, and the step will fail
# - exitAtEnd -> the action will go on, every pathspec error will be logged at the end, the step will fail.
# Default: ignore
pathspec_error_handling: error