Skip to content

feat: align hook lifecycle with upstream Codex (v1.5.0) - #99

Merged
sf-jin-ku merged 4 commits into
mainfrom
feat/native-hook-lifecycle-alignment
Aug 30, 2026
Merged

feat: align hook lifecycle with upstream Codex (v1.5.0)#99
sf-jin-ku merged 4 commits into
mainfrom
feat/native-hook-lifecycle-alignment

test: cover real SessionEnd hook dispatch end to end

df064f9
Select commit
Loading
Failed to load commit list.
Sendbird Hawkman / Hawkman: Find and verify secrets succeeded Aug 30, 2026 in 6s

✅ No secret found

Details

How should I remove sensitive data from a pull request (PR)?

1. Delete and Regenerate the Key(recommended):

  • Regenerate new keys.
  • Invalidate the existing ones to prevent unauthorized access.

2. Force Overwrite the Commit:

  • Remove the sensitive information and commit the modified file.
  • Use git rebase -i HEAD~i or git revert <commit hash> to modify the commit history.
  • Force push the changes (git push --force).
    Use git push --force cautiously to avoid data loss and collaboration issues; always notify your team.

3. Contact the Administrator:

  • Report the commit and file containing sensitive information to the administrator.
  • Follow the administrator's instructions.
  • Receive additional instructions if necessary.
    Not detected secret

When the PR is blocked but It has to be merged

If you have an emergency and need to merge the PR, please contact a github admin, the github admins are listed in https://github.com/orgs/sendbird/teams/github_admins