Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-114: Lock down bug tracker to developers only #120

Merged
merged 4 commits into from
Aug 1, 2024

Conversation

cmb69
Copy link
Member

@cmb69 cmb69 commented Jul 20, 2024

All further conversation about bugs is supposed to happen on Github. We still allow developers to edit the bug tracker, so they can clean up.

We start by disallowing users to add patches.

TODO:


Note that I do not have a development environment for web-bugs, so this is completely untested. Maybe somebody with a development environment can check this? (and perhaps even help to solve further tasks)

All further conversation about bugs is supposed to happen on Github.
We still allow developers to edit the bug tracker, so they can clean
up.

We start by disallowing users to add patches.
@cmb69 cmb69 linked an issue Jul 20, 2024 that may be closed by this pull request
@cmb69
Copy link
Member Author

cmb69 commented Jul 20, 2024

Note that I took (almost) no effort to clean up dead code (the whole CAPTCHA might not be needed anymore, and likely there is more dead code); that might be done later, or never be done at all.

Otherwise I think this PR is ready for review.

@cmb69 cmb69 marked this pull request as ready for review July 20, 2024 16:44
@php-pulls
Copy link

php-pulls commented Jul 20, 2024 via email

@cmb69
Copy link
Member Author

cmb69 commented Jul 20, 2024

Fair point! I've sent a respective mail to php-webmasters and internals.

@derickr
Copy link
Member

derickr commented Jul 22, 2024

Heh, why does that show as php-pulls, and not as me. I wonder.

@cmb69
Copy link
Member Author

cmb69 commented Jul 22, 2024

Maybe your email address is associated with that user?

@cmb69
Copy link
Member Author

cmb69 commented Jul 29, 2024

Maybe somebody with a development environment can check this?

Does anybody have a developement environment for web-bugs set up? I'd rather not commit completely untested changes, but I still think that we should proceed here.

@derickr
Copy link
Member

derickr commented Jul 29, 2024 via email

@cmb69
Copy link
Member Author

cmb69 commented Jul 29, 2024

No need to hurry. Thank you!

@derickr
Copy link
Member

derickr commented Jul 29, 2024 via email

@derickr
Copy link
Member

derickr commented Jul 31, 2024

There are actually tests!

@derickr
Copy link
Member

derickr commented Jul 31, 2024

I can't find any issues with this patch, but I am not sure if I have tested every path — could you perhaps list the ones, as there seem to be more than the four checkboxes.

Copy link
Member

@derickr derickr left a comment

Choose a reason for hiding this comment

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

LGTM, except for the single comment.

Copy link
Member Author

@cmb69 cmb69 left a comment

Choose a reason for hiding this comment

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

Some comments about what the changes are supposed to do.

Comment on lines -1112 to +1109
echo "<p><a href='patch-add.php?bug_id={$bug_id}'>Add a Patch</a></p>";
if ($logged_in) {
echo "<p><a href='patch-add.php?bug_id={$bug_id}'>Add a Patch</a></p>";
}
Copy link
Member Author

Choose a reason for hiding this comment

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

Only show "add a patch" button for developers, now.

Copy link
Member

Choose a reason for hiding this comment

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

Also tested, and fine.

There is also still a link "add pull request" in the same fashion though (line 1116 below), but I guess we can leave that one?

Copy link
Member Author

Choose a reason for hiding this comment

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

This is an open issue in the OP's todo list. I think we should still allow to link PRs (they do no real harm), although that is debatable.

Copy link
Member

@derickr derickr left a comment

Choose a reason for hiding this comment

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

I think this looks good. Merge it?

Comment on lines -1112 to +1109
echo "<p><a href='patch-add.php?bug_id={$bug_id}'>Add a Patch</a></p>";
if ($logged_in) {
echo "<p><a href='patch-add.php?bug_id={$bug_id}'>Add a Patch</a></p>";
}
Copy link
Member

Choose a reason for hiding this comment

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

Also tested, and fine.

There is also still a link "add pull request" in the same fashion though (line 1116 below), but I guess we can leave that one?

@cmb69
Copy link
Member Author

cmb69 commented Aug 1, 2024

IMO, this is good as is. The issue about linking PRs could be addressed later, if need be.

@derickr derickr merged commit dc639be into php:master Aug 1, 2024
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.

Lock down bugs.php.net to only developer accounts
3 participants