Update main CI job to have name

[posborne]

Right now, GitHub is not showing an option in branch protection rules for this job to be completed as a status check. While I have not seen anything explicitly documented that having unnamed or generic job ids (e.g. build) will cause this to happen, there are recommendations to have jobs be uniquely named to avoid ambiguity and potential problems.

This change will need to land on main for us to know whether it resolves the problem. Feel free to take a gander at the rules to make sure I'm not missing something obvious as well @erikrose -- what I observed is that PRs are able to be merged before CI completes. Not the end of the world, but makes it easier for a goof to make it into main.

[erikrose]

Let's give the simple thing a shot before doing a deep perusal!

[posborne]

Right now, GitHub is not showing an option in branch protection rules for this job to be completed as a status check. While I have not seen anything explicitly documented that having unnamed or generic job ids (e.g. build) will cause this to happen, there are recommendations to have jobs be uniquely named to avoid ambiguity and potential problems.

This change will need to land on main for us to know whether it resolves the problem. Feel free to take a gander at the rules to make sure I'm not missing something obvious as well @erikrose -- what I observed is that PRs are able to be merged before CI completes. Not the end of the world, but makes it easier for a goof to make it into main.

[erikrose]

Let's give the simple thing a shot before doing a deep perusal!

[posborne]

Right now, GitHub is not showing an option in branch protection rules for this job to be completed as a status check. While I have not seen anything explicitly documented that having unnamed or generic job ids (e.g. build) will cause this to happen, there are recommendations to have jobs be uniquely named to avoid ambiguity and potential problems.

This change will need to land on main for us to know whether it resolves the problem. Feel free to take a gander at the rules to make sure I'm not missing something obvious as well @erikrose -- what I observed is that PRs are able to be merged before CI completes. Not the end of the world, but makes it easier for a goof to make it into main.

[erikrose]

Let's give the simple thing a shot before doing a deep perusal!

[posborne]

Right now, GitHub is not showing an option in branch protection rules for this job to be completed as a status check. While I have not seen anything explicitly documented that having unnamed or generic job ids (e.g. build) will cause this to happen, there are recommendations to have jobs be uniquely named to avoid ambiguity and potential problems.

This change will need to land on main for us to know whether it resolves the problem. Feel free to take a gander at the rules to make sure I'm not missing something obvious as well @erikrose -- what I observed is that PRs are able to be merged before CI completes. Not the end of the world, but makes it easier for a goof to make it into main.

[erikrose]

Let's give the simple thing a shot before doing a deep perusal!

[posborne]

Right now, GitHub is not showing an option in branch protection rules for this job to be completed as a status check. While I have not seen anything explicitly documented that having unnamed or generic job ids (e.g. build) will cause this to happen, there are recommendations to have jobs be uniquely named to avoid ambiguity and potential problems.

This change will need to land on main for us to know whether it resolves the problem. Feel free to take a gander at the rules to make sure I'm not missing something obvious as well @erikrose -- what I observed is that PRs are able to be merged before CI completes. Not the end of the world, but makes it easier for a goof to make it into main.

[erikrose]

Let's give the simple thing a shot before doing a deep perusal!

[posborne]

Right now, GitHub is not showing an option in branch protection rules for this job to be completed as a status check. While I have not seen anything explicitly documented that having unnamed or generic job ids (e.g. build) will cause this to happen, there are recommendations to have jobs be uniquely named to avoid ambiguity and potential problems.

This change will need to land on main for us to know whether it resolves the problem. Feel free to take a gander at the rules to make sure I'm not missing something obvious as well @erikrose -- what I observed is that PRs are able to be merged before CI completes. Not the end of the world, but makes it easier for a goof to make it into main.

[erikrose]

Let's give the simple thing a shot before doing a deep perusal!

[posborne]

Right now, GitHub is not showing an option in branch protection rules for this job to be completed as a status check. While I have not seen anything explicitly documented that having unnamed or generic job ids (e.g. build) will cause this to happen, there are recommendations to have jobs be uniquely named to avoid ambiguity and potential problems.

This change will need to land on main for us to know whether it resolves the problem. Feel free to take a gander at the rules to make sure I'm not missing something obvious as well @erikrose -- what I observed is that PRs are able to be merged before CI completes. Not the end of the world, but makes it easier for a goof to make it into main.

[erikrose]

Let's give the simple thing a shot before doing a deep perusal!

[posborne]

Right now, GitHub is not showing an option in branch protection rules for this job to be completed as a status check. While I have not seen anything explicitly documented that having unnamed or generic job ids (e.g. build) will cause this to happen, there are recommendations to have jobs be uniquely named to avoid ambiguity and potential problems.

This change will need to land on main for us to know whether it resolves the problem. Feel free to take a gander at the rules to make sure I'm not missing something obvious as well @erikrose -- what I observed is that PRs are able to be merged before CI completes. Not the end of the world, but makes it easier for a goof to make it into main.

[erikrose]

Let's give the simple thing a shot before doing a deep perusal!