It looks like you're doing two jobs here. One is building the images for your modified repo, and the other is hosting the images (so that your server can use them).
You can use any tool appropriate for this, for the second part (image hosting) the default image for self-host servers is at quay.io/forem/forem:latest - but you can use the foremimg command to point that at dockerhub (see forem.dev/andrewbrown/how-to-keep-... for example, he uses the default repo location but that's the same process to change it).
For the first part (building the image, which is the stage you're reporting a problem with) I don't know of anything special about our setup (we use buildkite, which runs the build_containers script I pointed to, but docker build locally in the checked out repo should work fine, and a build process able to checkout your code branch, and build images from that, and push to the repository of your choice, should work).
For further actions, you may consider blocking this person and/or reporting abuse
It looks like you're doing two jobs here. One is building the images for your modified repo, and the other is hosting the images (so that your server can use them).
You can use any tool appropriate for this, for the second part (image hosting) the default image for self-host servers is at quay.io/forem/forem:latest - but you can use the
foremimgcommand to point that at dockerhub (see forem.dev/andrewbrown/how-to-keep-... for example, he uses the default repo location but that's the same process to change it).For the first part (building the image, which is the stage you're reporting a problem with) I don't know of anything special about our setup (we use buildkite, which runs the build_containers script I pointed to, but docker build locally in the checked out repo should work fine, and a build process able to checkout your code branch, and build images from that, and push to the repository of your choice, should work).