Open gentlementlegen opened 3 days ago
/help
Command | Description | Example |
---|---|---|
/help |
List all available commands. | /help |
Command | Description | Example |
---|---|---|
/help |
List all available commands. | /help |
/allow |
Allows the user to modify the given label. | /allow @user1 label |
/query |
Returns the user's wallet, access, and multiplier information. | /query @UbiquityOS |
/start |
Assign yourself to the issue. | /start |
/stop |
Unassign yourself from the issue. | /stop |
/wallet |
Register your wallet address for payments. | /wallet ubq.eth |
https://dash.cloudflare.com/${env.CLOUDFLARE_ACCOUNT_ID}/workers/services/view/${env.CLOUDFLARE_WORKER_NAME}/production/observability/logs?granularity=0&time=${timeParam}
However this would require worker deployments to upload these values as they are not accessible through a worker by default. What do you think?
If yes, it should be its own task I believe.
_Originally posted by @gentlementlegen in https://github.com/ubiquity-os/ubiquity-os-kernel/pull/169#discussion_r1821942110_
postComment
can post the url for an Action worker, but doesn't not have context for a Worker run. What could be done is adding a url to the dashboard with the time of the run as a filter so that we instantly have the related logs displayed.Code snippet:
This would imply uploading
CLOUDFLARE_ACCOUNT_ID
andCLOUDFLARE_WORKER_NAME
during worker deployment as these values are not available by default.To achieve this, a new reusable GitHub action could be created to avoid having to modify each upload script from every worker plugin. This would greatly benefit all the projects and make deployment simpler.