Oneseco Media GITHUB

Google Sites cheat sheet Build internal project hubs, team sites, & public-facing websites. Get Sites: Web (sites.google.com) Start a new site From Sites, click , or, to choose a template, click Template gallery and select a template. Customize your site and home page   Add a site name (name of the site file in Drive)   Add a site title for the public   Add a home page title   Choose a background image   Return to original background image   Choose a header type   Choose a theme   Choose a background color   Choose a font style Add pages and navigation   Choose your site navigation location and add page links   Drag pages up and down to re-order, or on top of another page to nest   Add a page or link             Add content to pages   Double-click on the page to add content   Add text, images, URLs, or Drive files   Add table of contents, carousels, buttons, a (horizontal) divider line, YouTube videos, calendars, and maps   Add documents, presentations, spreadsheets, forms, or charts                               Share, preview, or publish your site Preview—See how your site will look on any device once it's live. Copy link—Copy published site link. Share—Share your site with your team to collaborate. Publish Set your site's complete URL and who can see the site, then make it live. Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated. Give feedback about this article

Getting started with a workflow To help you get started, this guide shows you some basic examples. For the full GitHub Actions documentation on workflows, see "Configuring workflows." Customizing when workflow runs are triggered Set your workflow to run on push events to the main and release/* branches on: push: branches: - main - release/* Set your workflow to run on pull_request events that target the main branch on: pull_request: branches: - main Set your workflow to run every day of the week from Monday to Friday at 2:00 UTC on: schedule: - cron: "0 2 * * 1-5" For more information, see "Events that trigger workflows." Manually running a workflow To manually run a workflow, you can configure your workflow to use the workflow_dispatch event. This enables a "Run workflow" button on the Actions tab. on: workflow_dispatch: For more information, see "Manually running a workflow." Running your jobs on different operating systems GitHub Actions provides hosted runners for Linux, Windows, and macOS. To set the operating system for your job, specify the operating system using runs-on: jobs: my_job: name: deploy to staging runs-on: ubuntu-22.04 The available virtual machine types are: ubuntu-latest, ubuntu-22.04, or ubuntu-20.04 windows-latest, windows-2022, or windows-2019 macos-latest, macos-13, or macos-12 For more information, see "Virtual environments for GitHub Actions." Using an action Actions are reusable units of code that can be built and distributed by anyone on GitHub. You can find a variety of actions in GitHub Marketplace, and also in the official Actions repository. To use an action, you must specify the repository that contains the action. We also recommend that you specify a Git tag to ensure you are using a released version of the action. - name: Setup Node uses: actions/setup-node@v4 with: node-version: '20.x' For more information, see "Workflow syntax for GitHub Actions." Running a command You can run commands on the job's virtual machine. - name: Install Dependencies run: npm install For more information, see "Workflow syntax for GitHub Actions." Running a job across a matrix of operating systems and runtime versions You can automatically run a job across a set of different values, such as different versions of code libraries or operating systems. For example, this job uses a matrix strategy to run across 3 versions of Node and 3 operating systems: jobs: test: name: Test on node ${{ matrix.node_version }} and ${{ matrix.os }} runs-on: ${{ matrix.os }} strategy: matrix: node_version: ['18.x', '20.x'] os: [ubuntu-latest, windows-latest, macOS-latest] steps: - uses: actions/checkout@v4 - name: Use Node.js ${{ matrix.node_version }} uses: actions/setup-node@v4 with: node-version: ${{ matrix.node_version }} - name: npm install, build and test run: | npm install npm run build --if-present npm test For more information, see "Workflow syntax for GitHub Actions." Running steps or jobs conditionally GitHub Actions supports conditions on steps and jobs using data present in your workflow context. For example, to run a step only as part of a push and not in a pull_request, you can specify a condition in the if: property based on the event name: steps: - run: npm publish if: github.event_name == 'push' For more information, see "Contexts and expression syntax for GitHub Actions."

Docs Why updates expire? URL Scheme API Security & Legal CleanShot Security Bug Bounty Program EULA CleanShot Cloud Terms of Service Privacy Policy Subprocessors DPA URL scheme API Our macOS app exposes actions that lets pro users and developers of other apps send commands to CleanShot. This page explains how it works. Overview URL scheme is a special type of link that works just like a normal https:// link you use every day. Instead of opening a webpage, it performs a specific action in the CleanShot macOS app. Commands are sent to CleanShot by constructing a special URL: cleanshot://command-name?parameter1=value1&parameter2=value2 Opening these links will launch the app and execute the command. For example, here's how you would tell CleanShot to take a fullscreen screenshot: cleanshot://capture-fullscreen ✨  All-In-One mode /all-in-one Launch the "All-In-One" mode. You can also provide the optional parameters to open the tool at specific location. Point (0,0) is located in the lower left corner of the screen. Parameters: x (optional) y (optional) width (optional) height (optional) display (optional) - Capture a specified display: 1 is the main display, 2 is the secondary, etc. If not specified, CleanShot will use the display which the cursor is on. Example: cleanshot://all-in-one or cleanshot://all-in-one?x=100&y=120&width=200&height=150&display=1 Requires CleanShot 4.2 or later. Parameters x, y, width, height, display require version 4.7 or later. 📸  Screenshots /capture-area Opens the standard "Capture Area" mode. You can also provide the optional parameters and capture the screen instantly. Point (0,0) is located in the lower left corner of the screen. Parameters: x (optional) y (optional) width (optional) height (optional) display (optional) - Capture a specified display: 1 is the main display, 2 is the secondary, etc. If not specified, CleanShot will use the display which the cursor is on. action (optional) - Perform a specific action after taking a screenshot: (copy/save/annotate/upload/pin). Example: cleanshot://capture-area or cleanshot://capture-area?action=annotate or cleanshot://capture-area?x=100&y=120&width=200&height=150&display=1 Requires CleanShot 3.5.1 or later. Parameter action requires version 4.7 or later. /capture-previous-area Repeats last taken screenshot. Parameters: action (optional) - Perform a specific action after taking a screenshot: (copy/save/annotate/upload/pin) Example: cleanshot://capture-previous-area Requires CleanShot 3.5.1 or later. Parameter action requires version 4.7 or later. /capture-fullscreen Takes a fullscreen screenshot. Parameters: action (optional) - Perform a specific action after taking a screenshot: (copy/save/annotate/upload/pin) Example: cleanshot://capture-fullscreen Requires CleanShot 3.5.1 or later. Parameter action requires version 4.7 or later. /capture-window Opens "Capture Window" mode. Parameters: action (optional) - Perform a specific action after taking a screenshot: (copy/save/annotate/upload/pin) Example: cleanshot://capture-window Requires CleanShot 3.5.1 or later. Parameter action requires version 4.7 or later. /self-timer Opens "Capture Area" mode with self-timer. Parameters: action (optional) - Perform a specific action after taking a screenshot: (copy/save/annotate/upload/pin) Example: cleanshot://self-timer Requires CleanShot 3.5.1 or later. Parameter action requires version 4.7 or later. /scrolling-capture Opens "Scrolling Capture" mode. You can also provide the optional parameters to open the tool at specific location. Point (0,0) is located in the lower left corner of the screen. Parameters: x (optional) y (optional) width (optional) height (optional) display (optional) - Capture a specified display: 1 is the main display, 2 is the secondary, etc. If not specified, CleanShot will use the display which the cursor is on. start (optional) - Automatically start capture (true/false) autoscroll (optional) - Enable auto-scroll mode (true/false) Example: cleanshot://scrolling-capture or cleanshot://scrolling-capture?x=100&y=120&width=200&height=150&start=true&autoscroll=true Requires CleanShot 3.5.1 or later. Parameters start and autoscroll require version 4.7 or later. /pin Opens the specified file as a pinned screenshot. Parameters: filepath (optional) - path to the file (PNG/JPEG) you want to pin. If you don’t pass this parameter, CleanShot will ask to select the file manually. Example: cleanshot://pin or cleanshot://pin?filepath=/Users/john/Desktop/my%20screenshot.png Requires CleanShot 3.5.1 or later. 🎥  Screen Recording /record-screen Opens "Record Screen" mode. You can also provide the optional parameters to open the tool at specific location. Point (0,0) is located in the lower left corner of the screen. Parameters: x (optional) y (optional) width (optional) height (optional) display (optional) - Capture a specified display: 1 is the main display, 2 is t