Your "e_commerce" service has a successful deployment currently running, but if new commits aren't appearing even when you manually trigger a deploy, the GitHub repo connection is likely stale. Go to your service's Settings tab, disconnect the repo, then reconnect it to kodzotech/e_commerce and verify that the correct branch is selected as the trigger branch. Also confirm at github.com/settings/installations that the Railway GitHub App has access to that repository.

Your GitHub connection is working fine. The issue is your Watch Paths setting on this service - it's set to "IPv6 Egress", which isn't a valid file path pattern, so no pushes will match it. Remove that watch pattern (or replace it with a valid path like /src/**) and auto-deploys should start working.