Update Stale Workflow

[Jdubrick]

What does this PR do?

Updates stale workflow to address older issues not being properly marked as stale. In the workflow we had a start_date which by their docs means any PR or issue opened before that date is not going to be checked. Additionally, added ascending: true so that it will start from the lowest issue # item and work its way to the newer ones, ensuring that the oldest issues are checked first.

Which issue(s) does this PR fix

fixes #1529
fixes #1528

PR acceptance criteria

Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

• Open new test/doc issues under the devfile/api repo
• Check each criteria if:
• There is a separate tracking issue. Add the issue link under the criteria
  or
• test/doc updates are made as part of this PR
• If unchecked, explain why it's not needed

• Unit/Functional tests

• QE Integration test

• Documentation

• Client Impact

How to test changes / Special notes to the reviewer

[Jdubrick]

Failing check unrelated to my changes, will rerun to see if it changes the outcome.

[thepetk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Jdubrick, thepetk

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Jdubrick]

@thepetk workflow keeps failing but I highly doubt it is because of the changes in this PR. Wdyt is the course of action?

[thepetk]

@thepetk workflow keeps failing but I highly doubt it is because of the changes in this PR. Wdyt is the course of action?

Ive noticed the same behaviour in other prs (similar error trace). Id suggest waiting a little bit before investigating as the PR is not so urgent and we can retest later. Wdyt?

[Jdubrick]

@thepetk workflow keeps failing but I highly doubt it is because of the changes in this PR. Wdyt is the course of action?

Ive noticed the same behaviour in other prs (similar error trace). Id suggest waiting a little bit before investigating as the PR is not so urgent and we can retest later. Wdyt?

Sounds good to me. Can give it some time and revisit on Monday, if the checks are still failing we can bring it up in standup about pushing through anyway if unrelated

[thepetk]

@thepetk workflow keeps failing but I highly doubt it is because of the changes in this PR. Wdyt is the course of action?

Ive noticed the same behaviour in other prs (similar error trace). Id suggest waiting a little bit before investigating as the PR is not so urgent and we can retest later. Wdyt?

Sounds good to me. Can give it some time and revisit on Monday, if the checks are still failing we can bring it up in standup about pushing through anyway if unrelated

Yeah I agree. Is very unlikely to be related with the PR :D

[thepetk]

/retest

[openshift-ci]

New changes are detected. LGTM label has been removed.

[Jdubrick]

@thepetk rebase and fixing some whitespace seemed to fix the issue. Weird but it did the trick. Can you re-review please?

[thepetk]

@thepetk rebase and fixing some whitespace seemed to fix the issue. Weird but it did the trick. Can you re-review please?

Very weird :D But yeah my review remains the same. Nice addition to the workflow!