Skip to content

Restore several PR-related features#9443

Merged
fregante merged 12 commits into
mainfrom
branchs
May 13, 2026
Merged

Restore several PR-related features#9443
fregante merged 12 commits into
mainfrom
branchs

Conversation

@SunsetTechuila
Copy link
Copy Markdown
Member

@SunsetTechuila SunsetTechuila commented May 12, 2026

Fixes:

  • actionable-pr-view-file
  • clean-conversation-headers
  • clear-pr-merge-commit-message
  • restore-file
  • update-pr-from-base-branch
  • pr-branch-auto-delete
  • pr-base-commit
  • conversation-activity-filter (on PRs)
image

Fixes this too:

#9443 (comment)

Test URLs

this PR

Screenshot

observe(
[
'span[class*="PullRequestHeaderSummary"]',
'[class*="PullRequestHeaderSummary"]',
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This is gonna select old PR branch links:

'[class*="PullRequestHeaderSummary"] > [class*="PullRequestHeaderSummary"]', // TODO: Remove after July 2026

'[class*="PullRequestHeaderSummary"] * [class*="PullRequestHeaderSummary"]', // TODO: Remove after July 2026

Copy link
Copy Markdown
Member Author

@SunsetTechuila SunsetTechuila May 12, 2026

Choose a reason for hiding this comment

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

We're supporting 4 (!) versions of the header element at this point: 3 React-based and a legacy one

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do remove anything that you can no longer see. GHE support is just a plus, as always.

@SunsetTechuila SunsetTechuila marked this pull request as ready for review May 12, 2026 12:07
@SunsetTechuila
Copy link
Copy Markdown
Member Author

SunsetTechuila commented May 12, 2026

clear-pr-merge-commit-message works only visually 👍

08cc4ce

@SunsetTechuila
Copy link
Copy Markdown
Member Author

We shouldn't have removed the input event dispatching: #9337 (comment)

@fregante
Copy link
Copy Markdown
Member

works only visually

#9337 (comment)

Trying to decrypt your messages, I suppose that the message is removed from the DOM, but it's not what's being submitted to the servers?

@SunsetTechuila
Copy link
Copy Markdown
Member Author

You decrypted it right

@SunsetTechuila SunsetTechuila changed the title Restore features depending on PR branch selectors Restore several PR-related features May 12, 2026

[class^='PullRequestBranchName'],
/* TODO: Remove after July 2026 */
/* Old views */ /* TODO: Drop after legacy PR files view is removed */
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Why does Malva format:

	[class^='PullRequestBranchName'],
	/* Old views */
	/* TODO: Drop after legacy PR files view is removed */
	.commit-ref,
	/* TODO: Drop after July 2026 */
	[class^='BranchName'] {
		font-size: 12px !important;
	}

as

	[class^='PullRequestBranchName'],
	/* Old views */ /* TODO: Drop after legacy PR files view is removed */
	.commit-ref,
	/* TODO: Drop after July 2026 */
	[class^='BranchName'] {
		font-size: 12px !important;
	}

I don't think this is right

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@g-plane can you take a look please? thank you in advance

playground

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

A bit redundant given the following comment

Suggested change
/* Old views */ /* TODO: Drop after legacy PR files view is removed */
/* TODO: Drop after legacy PR files view is removed */

@fregante
Copy link
Copy Markdown
Member

What happened here? Did they just change the selectors? I used restore-file until yesterday

@SunsetTechuila
Copy link
Copy Markdown
Member Author

SunsetTechuila commented May 12, 2026

Did they just change the selectors?

They changed the DOM a bit today

@SunsetTechuila SunsetTechuila linked an issue May 12, 2026 that may be closed by this pull request
1 task
@fregante
Copy link
Copy Markdown
Member

By the way I'll release a new version this week because of this. Maybe in a day or two. Do you reckon they changed the DOM for good?

'[class*="PullRequestHeaderSummary"] a[class^="PullRequestBranchName"]',
'[class*="PullRequestHeaderSummary"] > [class*="PullRequestHeaderSummary"]', // TODO: Remove after July 2026
'.base-ref', // TODO: Remove in June 2026
'.base-ref', // TODO: Drop after legacy PR files view is removed
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🙌

@SunsetTechuila
Copy link
Copy Markdown
Member Author

SunsetTechuila commented May 13, 2026

Do you reckon they changed the DOM for good?

What do you mean?

@fregante
Copy link
Copy Markdown
Member

Basically I'm worried that they will revert these DOM changes after we publish this PR 😂

@SunsetTechuila
Copy link
Copy Markdown
Member Author

The changes I made are backwards compatible

@fregante
Copy link
Copy Markdown
Member

Ready to merge?

@fregante
Copy link
Copy Markdown
Member

Ready or not, here I come.

With restore-file broken, Refined GitHub is useless to me 😃

I'll release a new version within the hour unless something comes up

@fregante fregante merged commit ed3769c into main May 13, 2026
13 checks passed
@fregante fregante deleted the branchs branch May 13, 2026 17:14
@SunsetTechuila
Copy link
Copy Markdown
Member Author

Ready

fregante pushed a commit that referenced this pull request May 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

pr-base-commit: Expected element not found

2 participants