fix:Automatically unlock issue (#6770)

[nitheesh-daram]

Fixes Issue

Resolves #6770

Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• My change requires changes to the documentation.
• I have updated the documentation accordingly.
• All new and existing tests passed.
• This PR does not contain plagiarized content.
• The title of my pull request is a short description of the requested changes.

Screenshots

When the 🚦 status: awaiting triage label is added, it auto-locks the issue :

When 🏁 status: ready for dev is added, auto unlocks the issue :

Note to reviewers

Replaced repo-lockdown with label-actions as label-actions has both lock and unlock functionality and developed by the same developer.

[nitheesh-daram]

Replaced repo-lockdown with label-actions as label-actions has both lock and unlock functionality and developed by the same developer.

Here two things happen

1. It will lock the issue when the 🚦 status: awaiting triage label is added, irrespective of other labels.
2. It will Unlock the issue when the 🏁 status: ready for dev label is added, irrespective of other labels.

[nitheesh-daram]

Looks like there's a bug where unlocking the issue goes unlocks -> locks again -> unlocks, will raise an issue in the label-actions repo.

Update : raised here dessant/label-actions#23

[nitheesh-daram]

Looks like there's a bug where unlocking the issue goes unlocks -> locks again -> unlocks, will raise an issue in the label-actions repo.

Update : raised here dessant/label-actions#23

This seems to happen only when you have a comment while unlocking an issue (Like we have)

[eddiejaoude]

Looks like there's a bug where unlocking the issue goes unlocks -> locks again -> unlocks, will raise an issue in the label-actions repo.
Update : raised here dessant/label-actions#23

This seems to happen only when you have a comment while unlocking an issue (Like we have)

Oh I see, is this a blocker for us to use it? Should we wait until it is fixed on the original repo?

[nitheesh-daram]

Oh I see, is this a blocker for us to use it? Should we wait until it is fixed on the original repo?

I think we are 2 options:

1. if we want a comment while unlocking, we need to wait for the new release (it's already fixed here(dessant/label-actions@8ebc35d) in the code part, but the owner has yet to release the new version).
2. if we don't want a comment while unlocking, we are good to go!

I would personally prefer option 2, as adding an extra comment while unlocking makes the issue thread unnecessarily long.

let me know, which one you think is best, and I'll make changes accordingly.

thanks

[eddiejaoude]

We do often comment, so we might have to wait for the release

[nitheesh-daram]

We do often comment, so we might have to wait for the release

Sure, Eddie, I'll watch the repo and make the changes when a new release comes out.

And also, let me know what you would like to have as a comment while unlocking !
I suggest making it informative, like linking to docs on commit style,pr creation, rather than normal comments.

[eddiejaoude]

Awesome! I will mark this as block for now, and we can unblock it when the fix is released 👍

I will check the text also 👍

[nitheesh-daram]

Awesome! I will mark this as block for now, and we can unblock it when the fix is released +1

I will check the text also +1

Hey Eddie, the developer released a new release, and it looks like we don't need any changes from our end; we are good to merge!

[nitheesh-daram]

We need to change this to something informative.

[eddiejaoude]

Awesome 👍 Thank you! I will tale a look at merging this tomorrow

[eddiejaoude]

Looks good 👍 , I will merge to a temporary branch and have a play