Race condition with auto-archive and item closed workflows

[arcane-p]

Select Topic Area

Bug

Feature Area

Projects

Body

Hello!

When using both the auto-archive items and item closed workflows, I believe we get slightly unintended behaviour.

What I would expect:

1. Trigger: Issue is closed
2. Item Closed workflow marks the item as Done
3. Auto-archive items archives the item in the Done state

What is seen:

1. Issue is closed
2. The Item is auto-archived as In Progress (the last state it was in)
3. The Item Closed workflow cannot modify the archived item and it remains In Progress and Archived.

This is likely because both the workflows have the same trigger conditions (is:issue is:closed)

What could be done:

1. Always make the auto-archive workflow to be the last to run if multiple workflows are triggered on the same Item
2. Alternatively, allow the Auto-archive Items workflow to be operated on item condition (e.g is:item is:done)

Hope this helps!

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐