Yes, when you’ve locked your deploy, it is locked until you manually choose another deploy to publish. If you have locked and keep making changes so new code is building, it will not be published.
If you are trying to notify developers on your team that something has been built / deployed but not published yet I believe you can use the Deploy Started hook, if you are trying to tell them that something new HAS been published as youve now manually set it to publish maybe you could use the Locked or Unlocked events to notify them of that change. (I remember reading somewhere that the deploy hooks might change to only those that are being published but at the moment I believe it is triggered for all deploys).
Also NOTE: You could follow Manage deploys | Netlify Docs
Whereby in commits you can use [skip ci] in the commit message to skip the deploy?