Skip to content
This repository has been archived by the owner on Mar 24, 2022. It is now read-only.

Fix and promote log output #306

Open
2 tasks
Mini256 opened this issue Mar 8, 2021 · 2 comments
Open
2 tasks

Fix and promote log output #306

Mini256 opened this issue Mar 8, 2021 · 2 comments
Labels
lifecycle/rotten type/refactor The issue or PR belongs to a refactor work.

Comments

@Mini256
Copy link
Member

Mini256 commented Mar 8, 2021 •
edited
Loading

Bug Report

I have searched the issues of this repository and believe that this is not a duplicate.

Related link

What is expected?

After ti-challenge-bot is upgraded to Probot 11, the method of log output has changed.

  • Check the output format of all log functions
  • Connected to the new log collection platform
@Mini256 Mini256 added the type/bug Categorizes issue or PR as related to a bug. label Mar 8, 2021
@Mini256 Mini256 changed the title Fix log output and Fix and promote log output Mar 8, 2021
@Mini256 Mini256 added type/refactor The issue or PR belongs to a refactor work. and removed type/bug Categorizes issue or PR as related to a bug. labels Mar 8, 2021
@Mini256 Mini256 mentioned this issue Mar 8, 2021
Merged
6 tasks
ti-chi-bot pushed a commit that referenced this issue Mar 10, 2021
@Mini256
feat: upgrade to probot v11.0.6 (#291)
20c0ee1 
### Related

- Resolve #298 
- Resolve #219 
- We need to update the logger in #306

### CheckedList

- [x] Use more explicit type definitions, such as in the context
- [x] Probot 11 rename `context.github` to `context.octokit`
- [x] Fix some unique index problems
- [x] Add types.ts
- [x] Sort import sentence, put together the same kind
- [x] Use `issueKey` and `pullKey` uniformly, no longer using `...context.issue()` directly to avoid invalidation of TS type checking
@ti-chi-bot
Copy link
Member

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle stale

@ti-chi-bot
Copy link
Member

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle rotten

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/rotten type/refactor The issue or PR belongs to a refactor work.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Mini256 @ti-chi-bot