chore(build): Copy go mod files first to leverage Docker layer cachin…

[obazoud]

…g for dependencies

[vercel]

@obazoud is attempting to deploy a commit to the Hookdeck Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Pull Request Overview

This PR optimizes the Docker build process by leveraging Docker layer caching for Go dependencies. The change reorders Dockerfile commands to copy Go module files first and download dependencies before copying the entire source code.

• Moves go.mod and go.sum copy operation before setting the working directory
• Adds explicit go mod download step to cache dependencies in a separate layer

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The WORKDIR command should be set before copying files. Currently, go.mod and go.sum are copied to the root directory (/) instead of the intended /app directory, which will cause the go mod download command to fail.

Suggested change

	COPY go.mod go.sum ./
	RUN go mod download
	WORKDIR /app
	WORKDIR /app
	COPY go.mod go.sum ./
	RUN go mod download

[alexluong]

Similar question to the message in another thread, would love to understand your use case here. Since I personally don't use this Dockerfile, I just want to understand the motivation.

Potentially, I think it may make sense to simply remove this Dockerfil instead if you can continue your workflow without. With that in mind, happy to proceed and support this if it helps.

I just think this Dockerfile is nowhere close to production-ready, and I want to avoid spending time maintaining an unused Dockerfile if we can avoid it.

[obazoud]

I’ve explained in the other thread how I use this Dockerfile in my local workflow to test my changes.