Bug 261905
| Summary: | [git-webkit] Need easier way to bypass commit security feature | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bfan2, jbedard, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=253354 | ||
Michael Catanzaro
I'm intentionally trying to publish an unembargoed commit from WebKit-security repo to the public WebKit repo, but:
$ git push
Pushing to origin, which is classified as a public remote
Verifying commits in 'default' mode
Attempting to push 1 batch of commits to origin...
'e960cdca5447' fixes a redacted issue, but 'origin' is a public remote
error: failed to push some refs to 'github.com:WebKit/WebKit.git
jbedard says currently the only way to publish the commit is to sabotage my git hook, because the intended solution requires access to radar. He suggests a Bugzilla-based solution is needed.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/116204116>