Feature Request / Bug? - Deployment ID

[steegecs]

I am not sure if what I am querying about is a feature request or a bug.

Basically, what I am trying to do is write a script to deploy all protocols and networks in my subgraph directory. Since I have multiple protocols/network deployments in a single directory, I want this script to only deploy to networks where code changes are relevant to a particular protocol/network deployment. What seems to happen at this point in time is that any code changes within my directory trigger the generation of a new deployment ID for all of my protocol/network deployments. I want the deployment ID generation to only generate a new ID for a specific protocol/network when a code change is relevant to that particular protocol/network deployment.

Here is an example:

When I make a change to the BSC, file in the Apeswap protocol folder, I want it to only generate a new deployment ID for the Apeswap BSC deployment upon running graph deploy. Instead, a new deployment ID will be generated when I deploy to any protocol/network. This includes Apeswap Matic, Uniswap-v2 Mainnet, Sushiswap Mainnet, etc. So if I only make a change to this BSC folder, and I run a script the deploys all protocols/networks in my directory, it will deploy all protocols/networks instead of just the Apeswap BSC subgraphs.

I can handle this be writing a script to monitor the files that are changed and only run specific deployments, however, I am thinking this feature is best installed in the generation of the deployment key, and I think will be quite useful for those who are managing many subgraphs.

Here is the repository I am working from:
https://github.com/steegecs/subgraphs/tree/steegecs/uniswap-forks-addForks/subgraphs/uniswap-forks

If you have any questions, please ask!

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.