[
https://issues.apache.org/jira/browse/DAFFODIL-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568151#comment-17568151
]
Steve Lawrence commented on DAFFODIL-2712:
------------------------------------------
Note, according to https://twitter.com/VirtusLab/status/1545407124234182656,
the scala steward instance is hosted by the scala team. So it's back, and
likely not going anywhere.
And I noticed that we have gotten pull requests updated for scala steward in
the past couple of weeks.
We should determine if there is an advantage to continue to this or switch to
the GitHub action approach. The scala steward config file does allow one to
specify how frequently to do PRs, just like GitHubActions.
But if we want to switch to process where it it manually triggered, the GitHub
approach is the only option via the "on: workflow_dispatch" option.
> Scala Steward no longer runs on Daffodil repo
> ---------------------------------------------
>
> Key: DAFFODIL-2712
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2712
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Steve Lawrence
> Priority: Major
>
> The Scala Steward Org instance was shutdown in June. The recommended way to
> create PR's for dependency updates is now using the Scala Steward github
> action. This was added for the daffodil-vscode repo here:
> https://github.com/apache/daffodil-vscode/pull/199/files
> We should do something similar for the daffodil repo.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
