#personalaccesstoken — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #personalaccesstoken, aggregated by home.social.
-
How To Create A Kubernetes (K8s) CPU or GPU Cluster On DigitalOcean https://youtu.be/c-X1qfcF4_M #Websplaining #Kubernetes #K8s #KubernetesCluster #Kubernete #k8Clusters #k8 #KuberneteClusters #DigitalOcean #Doctl #Kubectl #API #PersonalAccessToken #CPU #GPU #DOKS
-
How To Create A Kubernetes (K8s) CPU or GPU Cluster On DigitalOcean https://youtu.be/c-X1qfcF4_M #Websplaining #Kubernetes #K8s #KubernetesCluster #Kubernete #k8Clusters #k8 #KuberneteClusters #DigitalOcean #Doctl #Kubectl #API #PersonalAccessToken #CPU #GPU #DOKS
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
-
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/