Question, how often is Scala steward meant to update PR's if the main/master branch is updated? Scala Steward has opened a PR at aiven/guardian-for-apache-kafka#140 however I noticed that it hasn't updated the PR even though the branch is out of date with the main branch.
I think github recently got a button to rebase a PR (without merging it in). If not and you have Mergify you can command it with a comment
Just closing and reopening a PR also updates it -- it will trigger CI to run with the updated future merge commit
I think github recently got a button to rebase a PR (without merging it in). If not and you have Mergify you can command it with a comment
Unfortunately I cannot do this because we have a rule on repository to only allow signed commits and rebasing someone else's PR removes the signing of the commit
I will see if closing and reopening the PR will work but there are going to be merge conflicts unless the branch that scala-steward created gets updated
Hmm wait, in my case there isn't any conflict
Other valid settings are "on-conflicts" (the default) and "never"
Hi Scala Steward team,
I'm looking at developing a version of Scala Steward that is run on a local repo and will create the PR with updates.
The use case that's motivating this is to solve the problem when an organisation doesn't want to use the
community Scala Steward and doesn't have the capacity or resources to run a self hosted version.
Is this something that a contribution that would be accepted?
@amaalali: you can do this today, scala-steward runs in Docker, and if you supply your own credentials and a limited set of repos to run on, you could do this from your laptop with little to no effort
Does anyone know how to set log level to DEBUG when using docker run? I have something like this which does not seem to be working, I'm still only seeing INFO level logs
#!/bin/sh
export STEWARD_DIR=~/sandbox/scala-steward
export LOGIN="xxx"
export EMAIL="xxx"
docker run -v $STEWARD_DIR:/opt/scala-steward -it fthomas/scala-steward:latest \
--workspace "/opt/scala-steward/workspace" \
--repos-file "/opt/scala-steward/repos.md" \
--repo-config "/opt/scala-steward/default.scala-steward.conf" \
--git-author-email ${EMAIL} \
--vcs-api-host "https://api.code.corp.xxx.com/" \
--vcs-login ${LOGIN} \
--git-ask-pass "/opt/scala-steward/.github/askpass/$LOGIN.sh" \
--env-var "SBT_OPTS=-Xmx7168m -Xss1024m -XX:MaxMetaspaceSize=512m" \
--env-var "JAVA_OPTS=-DLOG_LEVEL=DEBUG" \
--do-not-fork \
--disable-sandbox
1 reply
I'm definitely happy to make a PR to clarify this FAQ question when using docker run if needed https://github.com/scala-steward-org/scala-steward/blob/main/docs/faq.md#how-can-i-change-log-levels
I have a workflow on my repo that is triggered by a
push event to any branch. For some reason, one of the pull requests created by a scala-steward-action run did not automatically kick off my github workflows. Has this happened to anyone else? Is this a fluke? Or do I need to listen to pull_request events as well for scala-steward?
Also, since https://github.com/scala-steward-org/repos is archived, what does the VirtusLab instance use? Can OSS projects be added to it?
I'm getting the above error using the default configuration specified at https://github.com/scala-steward-org/scala-steward-action#updating-multiple-repositories
Does anybody know how to fix this?
Does anybody know how to fix this?
For example, if something changed on master that would change the result of
sbt githubWorkflowGenerate
(the operation in question needs to be applied to ~40+ repos)
Still, can you script it with the github CLI?
@dkichler
Of course, first make sure that a clean clone of your repo loads.
How do I stop scala-steward updates of random github repositories show up in my main github page. Context: I added my project into scala steward repos and now my page is inundated with all sorts of dependency version updates to projects I have never even heard off. The only options I seem to have are "Block User" and "Report Abuse" neither of which I want to use.
Thats just one. My github page is flooded by these. I dunno if github is doing this or scala steward. The three dots on the side suggest either flagging scala steward for abuse or blocking the user entirely from contributing, neither of which I want.
You're on the "For you (beta)" tab?
Also Send feedback ;)
under Filter turn of Repositories seems to work for me
(I never use the main github page though)
Click Send feedback ;)