Skip to content

Commit

Permalink
chore: use naming convention for workflows (#118)
Browse files Browse the repository at this point in the history
* use naming convention for workflows

* use different prefix
  • Loading branch information
masci authored Dec 18, 2023
1 parent b79939a commit 5e8fe22
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 9 deletions.
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: "Labeler"
name: Core / Labeler
on:
- pull_request_target

Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: Track issues with Github project
name: Core / Add issues to Github project

on:
issues:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,13 +1,12 @@
name: Project release on PyPi
name: Core / Project release on PyPi

# The pushed tag must be formatted like so:
# * nodes/speech2text-v1.0.0
# * stores/foo-documentstore-v1.2.3
# * integrations/<INTEGRATION_FOLDER_NAME>-v1.0.0
#
# The first part must be the path of the project being released.
# If we want to release version 1.0.0 of project text2speech
# that lives in path nodes/text2speech we'd have to push a
# nodes/text2speech-v1.0.0 tag.
# For example, if we want to release version 1.0.99
# of the google-vertex-haystack integration we'd have to push the tag:
#
# integrations/google_vertex-v1.0.99

on:
push:
Expand Down

0 comments on commit 5e8fe22

Please sign in to comment.