Skip to content

Conversation

@marusak
Copy link
Contributor

@marusak marusak commented Jan 18, 2024

No description provided.

@marusak marusak force-pushed the fixes-correct_repo branch from 10c61e8 to bd2e16d Compare January 22, 2024 08:02
@ochosi ochosi self-requested a review January 24, 2024 09:38
Copy link
Collaborator

@ochosi ochosi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marusak I'd prefer it if the two changes went into separate PRs. The markdown support looks super straightforward (apart from parts of the code feeling like duplication), so I'd love to get that in asap to enable your team to use this!

# 4. Needs conflict resolution or rebasing
elif (not pull_request['changes_requested'] and
(pull_request['mergeable_state'] in {'dirty', 'behind'})):
elif (pull_request['mergeable_state'] in {'dirty', 'behind'}):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand and agree with the motivation for this change, but won't this lead to PRs showing up twice on the list?

Copy link
Collaborator

@ochosi ochosi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's split this into two PRs, one for markdown and one for relaxing the rules

@marusak
Copy link
Contributor Author

marusak commented Feb 12, 2024

Sent #34

@marusak marusak marked this pull request as draft February 12, 2024 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants