url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://aws.amazon.com/amplify | Full Stack Development - Web and Mobile Apps - AWS Amplify Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Amplify Overview Features Pricing Getting Started Customers Product › Front-End Web and Mobile › AWS Amplify Fullstack TypeScript. Frontend DX for AWS. AWS Amplify is everything you need to build web and mobile apps. Easy to start, easy to scale. Deploy an app Try a hands-on tutorial Go from idea to app in hours Deploy server-side rendered and static frontend apps, develop UI, add features like auth and storage, connect to real-time data sources, and scale to millions of users. No cloud expertise required. Play Deploy web frameworks globally Deploy an app frontend with easy Git-based workflows and support for any server-side web framework. Zero-config Next.js and Nuxt deployments offer global availability, reliability, and lower latency from the Amazon CloudFront Global Edge Network in just a few clicks. Fully-managed CI/CD and automatic scale make pushing new features to high-traffic web applications seamless. Learn about Amplify Hosting Go from frontend to fullstack, fast With fullstack TypeScript capabilities, Amplify brings the power and breadth of AWS services to a familiar frontend developer experience. Simply author app requirements like data models, business logic, and auth rules in TypeScript. Amplify automatically configures the correct cloud resources and deploys them to per-developer cloud sandbox environments for fast, local iteration. Build fullstack apps with TypeScript Commit, collaborate, and ship confidently Easily spin up new environments by connecting branches from Git. Pull request previews allow team members to test changes and merge to production with confidence. At deployment, managed CI/CD pipelines with fullstack branching require zero configuration. Learn about fullstack workflows Amplify features Data Build secure, real-time APIs backed by AWS databases quickly and easily. Connect your app to data Auth Enable secure authentication flows and control access to data, files, and more. Enable authentication and authorization Storage Store and manage app content and data. Build a backend with storage Functions Add functions and configure environment variables. Get started with functions Extensibility Add, extend, and customize any AWS service by simply authoring CDK code. Learn about Amplify + CDK Mobile Leverage a single backend across web and mobile apps. Learn about Amplify for Flutter Works with frameworks and languages you love What can you build with Amplify? SSR web applications Deploy and host server-side rendered applications with Next.js and Nuxt for improved performance and SEO. Implement server-side actions with data and middleware-protected authentication for routes with Amplify's JavaScript library. Single page web apps and static websites Deploy your app frontend to the globally-distributed AWS Content Delivery Network (CDN) with automated CI/CD across hundreds of edge locations. Add full-stack logic with authentication, authorization, storage, and data. Native mobile applications Build native iOS and Android apps in Swift, Kotlin, or Java with authentication, data, storage, and push notifications using Amplify's frontend Libraries and backend provisioning. Cross-platform applications Build cross-platform Flutter and React Native apps with capabilities like user authentication, data, and storage using Amplify's Libraries and backend resources. How to get started Read the Amplify docs Learn more Connect with an expert Learn more Sign up for an AWS account Learn more Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:41 |
https://support.microsoft.com/cs-cz/office/co-jsou-sm%C4%9Bny-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | Co jsou Směny? - Podpora Microsoftu Související témata × Výukové video k Microsoft Teams Microsoft Teams – úvodní příručka Co je Microsoft Teams? Přihlášení a zahájení práce Chatování a sdílení souborů Spolupráce Další informace Úvod do aplikace Microsoft Teams Začínáme s aplikací Microsoft Teams Začínáme s Chatem Začínáme se Schůzkami Začínáme s Aplikacemi Nastavte si tým podle vlastních představ Vytvoření týmu pomocí šablon Práce s externími hosty Správa nastavení týmu Spolupráce v týmech a kanálech Tip: Odeslání e-mailu na kanál Vytvoření plánu pomocí Planneru Práce s příspěvky a zprávami Odeslání zprávy do více kanálů Vyhledávání souborů Odesílání a sdílení souborů Hledání a filtrování lidí a souborů Hledání a filtrování zpráv Tipy k souborům Teams Zahájení chatů a hovorů Přehled hovorů přes Teams Volání Tipy k používání Teams Skrytí chatů a odstranění zpráv Nastavení delegáta pro přijímání hovorů Správa schůzek Připojení se ke schůzce Teams Tipy ke schůzkám v Teams Okamžitá schůzka Správa schůzek Naplánování webináře Sdílení obrazovky během schůzky Nastavení a zúčastnění se živých událostí Naplánování živé události Vytvoření živé události Zúčastnit se živé události Moderování Q&A Podrobnosti o aplikacích a nástrojích Vyhledat a používat aplikace Správa týmových plánů v Shifts Co jsou Směny? Vytvoření plánu Směn Správa plánu Směn Vytváření schválení Co jsou schválení? Vytvoření schválení Vytvoření schválení z chatu Vytvoření schválení z elektronického podpisu Objevte šablony v Centru schválení Vytvoření schválení pomocí šablon Vytvoření šablon pro celou organizaci Virtuální schůzky v Microsoft Bookings Co jsou virtuální schůzky? Odesílat externím hostům SMS textová upozornění Provedení schůzky Připojit se k události Správa informačního kanálu o aktivitách Správa nastavení oznámení Aplikace Teams na cestách Zahajte nový chat na cestách Vytvoření kanálu na cestách Připojení ke schůzce na cestách Informační kanál na cestách Přeskočit na hlavní obsah Microsoft Podpora Podpora Podpora Domů Microsoft 365 Office Podpora Teams Témata Schůzky Chat Oznámení & nastavení Týmy a kanály Hovory & zařízení Soubory Aplikace & služby Představení aplikace Chat Skupinový chat Oznámení Teams Kanály Hovory Soubory Aplikace Součásti Loop Co je nového Prostředky Instruktážní video Řešení potíží Tady v Teams Usnadnění Funkce Teams podle platformy Microsoft Teams (volná verze) Komunitní fóra Blog technické komunity Školení vedené instruktorem Pro správce a IT profesionály Pro vzdělávání Více Koupit Microsoft 365 Vše od Microsoftu Global Microsoft 365 Teams Copilot Windows Surface Xbox Nabídky Podpora Software Software Aplikace pro Windows Umělá inteligence OneDrive Outlook Přechod ze Skypu na Teams OneNote Microsoft Teams Počítače a zařízení Počítače a zařízení Koupit Xbox Příslušenství Zábava Zábava Xbox Game Pass Ultimate Konzole Xbox a hry Hry pro PC Nabídky pro firmy Nabídky pro firmy Microsoft Security Azure Dynamics 365 Microsoft 365 pro firmy Microsoft Industry Microsoft Power Platform Windows 365 Vývojáři a IT Vývojáři a IT Microsoft pro vývojáře Microsoft Learn Podpora aplikací s umělou inteligenci v obchodě Marketplace Odborná komunita Microsoft Microsoft Marketplace Visual Studio Marketplace Rewards Další Další Zdarma ke stažení a zabezpečení Vzdělávání Dárkové karty Zobrazit mapu stránek Hledat Hledat nápovědu Žádné výsledky Zrušit Přihlásit se Přihlásit se pomocí účtu Microsoft Přihlaste se nebo si vytvořte účet. Dobrý den, Vyberte jiný účet. Máte více účtů. Zvolte účet, pomocí kterého se chcete přihlásit. Související témata Výukové video k Microsoft Teams Microsoft Teams – úvodní příručka Co je Microsoft Teams? Přihlášení a zahájení práce Chatování a sdílení souborů Spolupráce Další informace Úvod do aplikace Microsoft Teams Začínáme s aplikací Microsoft Teams Začínáme s Chatem Začínáme se Schůzkami Začínáme s Aplikacemi Nastavte si tým podle vlastních představ Vytvoření týmu pomocí šablon Práce s externími hosty Správa nastavení týmu Spolupráce v týmech a kanálech Tip: Odeslání e-mailu na kanál Vytvoření plánu pomocí Planneru Práce s příspěvky a zprávami Odeslání zprávy do více kanálů Vyhledávání souborů Odesílání a sdílení souborů Hledání a filtrování lidí a souborů Hledání a filtrování zpráv Tipy k souborům Teams Zahájení chatů a hovorů Přehled hovorů přes Teams Volání Tipy k používání Teams Skrytí chatů a odstranění zpráv Nastavení delegáta pro přijímání hovorů Správa schůzek Připojení se ke schůzce Teams Tipy ke schůzkám v Teams Okamžitá schůzka Správa schůzek Naplánování webináře Sdílení obrazovky během schůzky Nastavení a zúčastnění se živých událostí Naplánování živé události Vytvoření živé události Zúčastnit se živé události Moderování Q&A Podrobnosti o aplikacích a nástrojích Vyhledat a používat aplikace Správa týmových plánů v Shifts Co jsou Směny? Vytvoření plánu Směn Správa plánu Směn Vytváření schválení Co jsou schválení? Vytvoření schválení Vytvoření schválení z chatu Vytvoření schválení z elektronického podpisu Objevte šablony v Centru schválení Vytvoření schválení pomocí šablon Vytvoření šablon pro celou organizaci Virtuální schůzky v Microsoft Bookings Co jsou virtuální schůzky? Odesílat externím hostům SMS textová upozornění Provedení schůzky Připojit se k události Správa informačního kanálu o aktivitách Správa nastavení oznámení Aplikace Teams na cestách Zahajte nový chat na cestách Vytvoření kanálu na cestách Připojení ke schůzce na cestách Informační kanál na cestách Co jsou Směny? Platí pro Teams Microsoft Teams Vyzkoušejte to! Aplikace Směny v Microsoft Teams je nástroj pro správu plánů a sledování času, který vám pomůže vytvářet, aktualizovat a spravovat plány pro váš tým. Plány – vytvořte, upravte a spravujte plán pro svůj tým. Plán Směny zobrazuje dny nahoře, členové týmu se zobrazují vlevo a přiřazené směny se zobrazují v kalendáři. Nastavení plánu – v nastavení směny definujte možnosti plánu a zvolte funkce Směny, které chcete zpřístupnit vašemu týmu. Skupiny – Přidejte skupiny plánů pro uspořádání členů týmu v plánu podle typu úlohy nebo umístění. Směny – přiřaďte směny členům týmu. Vytvořte posun od začátku nebo zkopírujte existující. Otevřené směny – každá skupina v plánu má řádek otevřených směn . Přidejte do svého plánu otevřené směny, o které si může požádat kdokoliv. Časové hodiny – Zapnutím funkce Časové hodiny v nastavení směny umožníte týmu, aby se směny vcháněly i odchádly. Žádosti – Zkontrolujte žádosti o volno, otevřené směny, výměny směn a nabídky a reagujte na ně. Značky – pomocí značek založených na směnách můžete rychle komunikovat s kýmkoli, kdo právě pracuje na směně. Publikování plánu – až dokončíte změny plánu, sdílejte ho se svým týmem, aby byli všichni aktuální. Chcete se dozvědět víc? Začínáme s aplikací Směny Vytvoření týmového plánu ve směnách Přidání směn do plánu ve Směnách Publikování plánu ve Směnách Správa žádostí o směny a volna ve Směnách Zapnutí značek založených na směnách v Teams PŘIHLÁSIT SE K ODBĚRU INFORMAČNÍCH KANÁLŮ RSS Potřebujete další pomoc? Chcete další možnosti? Zjišťování Komunita Prozkoumejte výhody předplatného, projděte si školicí kurzy, zjistěte, jak zabezpečit své zařízení a mnohem více. Výhody předplatného Microsoft 365 Školení k Microsoft 365 Zabezpečení od Microsoftu Centrum přístupnosti Komunity vám pomohou klást otázky a odpovídat na ně, poskytovat zpětnou vazbu a vyslechnout odborníky s bohatými znalostmi. Zeptejte se v komunitě Microsoftu Technická komunita Microsoftu Účastníci programu Windows Insider Účastníci programu Microsoft 365 Insider Byly tyto informace užitečné? Ano Ne Děkujeme! Máte nějakou další zpětnou vazbu pro Microsoft? Můžete nám pomoct službu zlepšit? (Pošlete Microsoftu svůj názor, abychom vám mohli pomoct.) Jak jste spokojeni s kvalitou jazyka? Co ovlivnilo váš názor? Vyřešilo to můj problém Jasné pokyny Snadný postup Bez žargonu Obrázky pomohly Kvalita překladu Neodpovídalo to mé obrazovce Nesprávné pokyny Příliš technické Nedostatek informací Nedostatek obrázků Kvalita překladu Máte další zpětnou vazbu? (Nepovinné) Odeslat názor Po stisknutí tlačítka pro odeslání se vaše zpětná vazba použije k vylepšování produktů a služeb Microsoftu. Váš správce IT bude moci tato data shromažďovat. Prohlášení o zásadách ochrany osobních údajů. Děkujeme vám za zpětnou vazbu. × Co je nového Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot pro organizace Copilot pro osobní používání Microsoft 365 Prohlédnout produkty Microsoft Microsoft Store Profil účtu Centrum stahování Podpora pro Microsoft Store Vrácení Sledování objednávky Recyklace Commercial Warranties Vzdělávání Microsoft Education Zařízení pro vzdělávání Microsoft Teams pro vzdělávání Microsoft 365 Education Office Education Vzdělávání a rozvoj pedagogů Akce pro studenty a rodiče Azure pro studenty Firmy Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Vývojáři a IT Microsoft pro vývojáře Microsoft Learn Podpora aplikací s umělou inteligenci v obchodě Marketplace Odborná komunita Microsoft Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Společnost Kariéra Novinky u společnosti Microsoft a ochrana osobních údajů Investoři Udržitelnost Čeština (Česko) Ikona nesouhlasu s volbami ochrany osobních údajů Vaše volby ochrany osobních údajů Ikona nesouhlasu s volbami ochrany osobních údajů Vaše volby ochrany osobních údajů Ochrana osobních údajů spotřebitele ve zdravotnictví Kontaktovat Microsoft Ochrana osobních údajů Spravovat soubory cookie Podmínky používání Ochranné známky O našich reklamách EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:41 |
https://www.digitalcameraworld.com/buying-guides/best-digital-photo-frames#section-best-statement-photo-frame | The best digital photo frames | Digital Camera World Skip to main content Open menu Close main menu Digital Camera World THE HOME OF DIGITAL PHOTOGRAPHY US Edition US Canada UK Australia Subscribe Sign in View Profile Sign out Search Search Digital Camera World Cameras Accessories Tech How To Reviews Buying Guides Magazines Bokeh Face Podcast The Photography & Video Show Digital Camera Australian Camera Australian ProPhoto About Us Photography Magazines Why subscribe? Issues filled with product reviews, latest updates, expert advice and more Delivered to your Android or IOS device Every issue is packed with photo tips, kit reviews and inspiration From $12 Subscribe now Jump to: The Quick List Best premium Best large Best high-res Best widescreen Best smart Best wall-hanging Best Wi-Fi Best budget Best statement How to choose How we test Don't miss these Phones The best camera phone: what's the best smartphone for photography? Compact Cameras The best compact cameras: top quality cameras you can take anywhere Digital Photo Frames This giant digital photo frame rearranges millions of ink capsules for a cord-free art display that can still display pictures when powered off! Printers The best portable printers: make real prints of your shots for sharing while you’re in the moment Scanners The best film scanners in 2025: negative and slide scanners that will give your old photos new life Cameras The best camera for beginners: Let me show you the right camera to start your shooting journey! Compact Cameras The best point and shoot camera in 2025: easy to use cameras to fit every pocket Digital Cameras The best retro cameras in 2026: get the classic camera vibe, but digitally! Camera Accessories Best camera glasses in 2025: wearable tech for eye-level photography Phones The top 10 camera phones of 2025: our standout handsets of the year Camcorders The best camcorders: perfect all-in-one video cameras Cameras The best Canon camera: Canon's top mirrorless, DSLRs and compacts Thermal Imaging Cameras The best thermal-imaging cameras in 2025 Cameras These are the best cameras for kids in 2026, as recommended by real photographer parents Instant Cameras The best instant cameras in 2025: Shoot stunning retro photographs with Instax, Polaroid and more Popular Camera news Camera rumors Photo mag deals Photography & Video Show Cheatsheets Tech Digital Photo Frames The best digital photo frames: show off your shots in style Buying guides By Adam Waring last updated 17 December 2025 Display all your favorite photos without printing them with the best digital photo frames, and there's one to suit every budget When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works . (Image credit: Hannah Rooke/Digital Camera World) Jump to: The Quick List Best premium Best large Best high-res Best widescreen Best smart Best wall-hanging Best Wi-Fi Best budget Best statement How to choose How we test Share Share by: Copy link Facebook X Whatsapp Pinterest Flipboard Share this article Join the conversation Follow us Add us as a preferred source on Google The best digital photo frames offer a great way to showcase your favorite photos. Instead of being limited to a single printed image, you can upload a selection of shots and enjoy them in rotation. A major advantage over traditional frames is the ability to instantly display new images – no more waiting for prints, and no need to buy a new frame for each update. Whether you're displaying pictures of family and friends, vacation memories, wedding photos, or even short videos, there's a digital frame that suits your needs. Today’s top digital frames are incredibly user-friendly. Unlike older models that require USB sticks or SD cards, all the frames in this guide are Wi-Fi-enabled and some store images in the cloud, allowing you to manage your gallery through a smartphone app. They variously use a touchscreen, touchbars, or a remote control to make navigation easy. So, how do you choose the best digital photo frame? There are numerous styles to pick from, but you’ll also want to consider factors like screen size, storage capacity, and support for video and sound. If it’s a gift, think about the recipient too – some frames can even be preloaded with images without opening up their box. Adam Waring Social Links Navigation Guides Editor Adam is the Guides Editor at Digital Camera World and has been working as a photography journalist for the past 15 years. He's long advocated that photographs need to be proudly displayed rather than hidden on hard drives and loves how easy digital photo frames make it to show off your best shots. The Quick List Best premium frame 1. Aura Aspen View at Target View at Amazon View at Nordstrom View at Best Buy With a super-sharp screen that shows your photos at their best and easy ways to add photos, this is a digital frame with class. Read more below… Best large frame 2. Aura Walden View at Amazon View at Amazon View at Nordstrom View at Best Buy Most digital photo frames are about 10 inches on the diagonal, but this one goes 50 per cent bigger, really showcasing your images on a big screen. Read more below… Best high-res frame 3. Pexar 11in View at Amazon View at Amazon View at Amazon View at Amazon Its 11in screen packs in a super-hi-res 2K display that shows the entire 100% Adobe sRGB color gamut, so your images really shine. Read more below… Best widescreen 4. Pexar Starlight View at Amazon View at Amazon If the 15.6-inch 16:9 ratio widescreen display wasn't statement enough, its 'Gallery Lighting' feature makes your photos really stand out with a golden glow. Read more below… Best for smart homes 5. Google Nest Hub View at Target View at Target Check Amazon Not only is this a capable (if small) photo frame, it also streams music and video, has an AI assistant, and sits in the center of your smart home. Read more below… Best wall-hanging 6. Aura Ink View at Aura Home Check Amazon With a built-in battery that lasts months and a natural-looking display that doesn't look like a screen, this wire-free frame is ideal for hanging on a wall. Read more below… View the full list ⤵ Best Wi-Fi frame 7. Aura Carver View at Amazon View at Amazon View at Camp Snap View at Camp Snap Adding photos via a smartphone app is the only method this frame offers, but the build and image quality are first-rate. Read more below… Best budget frame 8. Aeezo Portrait View at Amazon View at Amazon For a very affordable price, this frame shows off your images nicely and has loads of storage for adding more photos. Read more below… Best statement frame 9. Pix-Star Lux 17-inch View at Amazon With an enormous 17-inch display and elaborate molded bezel, this is one photo frame that demands attention. Read more below… Best digital photo frames Why you can trust Digital Camera World Our expert reviewers spend hours testing and comparing products and services so you can choose the best for you. Find out how we test. Best premium photo frame (Image credit: Future) 1. Aura Aspen A top-quality digital photo frame that makes a great gift Our expert review: Specifications Resolution: 1600 x 1200 (170ppi) Display: 11.8-inch Orientation: Landscape and portrait Dimensions: 12.7 x 10.1 x 1.1in Touch screen: No, but has touch bars Wi-Fi: Yes Remote: No Built-in storage: No Motion sensor: Yes Video: Yes USB/SD slots: No/No Cloud services: Instagram, Google Photos, Aura App Today's Best Deals View at Target View at Amazon View at Nordstrom View at Best Buy Reasons to buy + High-density 1600 x 1200, 170ppi, 12in display + Swipe bars avoid finger smudges + Unlimited photo (and video) storage Reasons to avoid - Pricier than many competitors - If your Wi-Fi goes down, so does the frame - No wall-hanging option Buy it if ✅ You want a crisp, clear display: the stunning 12-inch, high-resolution display auto dims to show images at their best ✅ You have a huge number of images: images are stored on Aura's servers rather than the frame itself, offering ulmited storage Don't Buy it if ❌ You want built-in storage: this only connects to could-services and via its own app to display images ❌ You want to hang it: the slim design tapers towards the frame edges, and as a result there's no wall-hanging option The Aura Aspen digital photo frame stands out from the crowd, offering several premium features at a competitive price point. Top of the list is its stunning 12-inch, 1600 x 1200 resolution display, which provides a crisp and vibrant viewing experience. Its minimalist design, available in Ink or Clay (black or gray), is enhanced by hidden Touch Bars for navigation, which helps to maintain a clean look by preventing fingerprints on the screen. It offers unlimited photo and video storage by backing up content to Aura's servers rather than storing it on the frame itself. This feature requires a constant Wi-Fi connection, but the benefit is the ability to display a vast number of photos without being limited by internal storage. The companion Aura app also makes it simple to crop and rotate images, share access with friends and family, and even pre-load photos for gifting. An auto-dimming light sensor that adjusts screen brightness to ambient light, and there's a built-in speaker for video playback. The only real drawback is the lack of a wall-mounting option, if that's your preference. Read more: Aura Aspen review Swipe to scroll horizontally Quality It looks like a real photo frame, with smart minimalist bezels and a textured 'card' inset 5 / 5 Features Auto dimming matches the ambient lighting and the hi-res display show of photos crisply, and managing images with the Aura app is easy 5 / 5 Value It's an upmarket frame and more expensive than some, but it's worth it 4 / 5 Today's best Aura Aspen deals $229 View $229 View $229.99 View Show more We check over 250 million products every day for the best prices Back to the top ⤴ Best large photo frame (Image credit: Future) 2. Aura Walden A real showstopper that's packed with features but comes at a price Our expert review: Specifications Resolution: 1600 x 1200 Display: 15 inches Orientation: Landscape and portrait Touchscreen: No, but has touch bars in bezel Wi-Fi: Yes Remote: No Built-in storage: None Card slots: None Cloud services: Aura Video: Yes Dimensions: ‎8.1 x 36.8 x 2.5cm Today's Best Deals View at Amazon View at Amazon View at Nordstrom View at Best Buy Reasons to buy + Stylish design suits modern decor + Can be preloaded with images for gifting + Images can be easily shared via app or uploaded from computers Reasons to avoid - No internal storage means no images if Wi-Fi goes down - 4:3 aspect ratio suits phones but not 'serious' cameras - One of the pricier frames around Buy it if ✅ You want a big screen: this large, stylish frame shows off images at their very best ✅ You want to gift it: it can be preloaded with pictures, and it's easy for additional users to share photos too Don't buy it if ❌ You're a pixel-peeper: many other frames comfortably exceed the Walden's 133ppi density ❌ You're strapped for cash: it's undeniably expensive and there are cheaper options out there When it comes to displaying photographs, bigger is almost always better, and the Aura Walden is a big frame that is big on features. The oversized 15-inch display shows off photographs in stunning detail and sits within a well-proportioned surround that is textured to look like a genuine photo frame and should look good in any home. Features such as auto-diming enable the display to suit the ambient lighting so that images are clear to see but not overly bright. The swipe bars are another nice touch, offering the ease of use of a touchscreen to navigate through images without getting greasy fingermarks over your photographs. It's super-easy to upload images from multiple users' phones, thanks to the companion Aura app, and the ability to preload photos for gifting is fantastically implemented. The pixel density perhaps could be a little higher, but a big frame demands admiring pictures from afar. It's undeniably expensive, but it's a luxurious frame and one of the best that money can buy. Read our full Aura Walden review Swipe to scroll horizontally Quality It's an elegant, classically styled frame the suits modern decor 5 / 5 Features 15in display is beautiful to behold; swipe bars save the screen from grubby fingerprints; easy to upload images 5 / 5 Value A big display comes with a big price tag, but it's still good value 4 / 5 Today's best Aura Walden 15 Inch Digital Photo Frame deals $299 View $299 View $299.99 View Show more We check over 250 million products every day for the best prices Back to the top ⤴ Best high-resolution photo frame (Image credit: Future) 3. Lexar Pexar 11in Beautiful hi-res screen and 100% sRGB color gamut should do even the finest of fine art photos justice Our expert review: Specifications Resolution: 2000 x 1200 Display: 11in Orientation: Landscape and portrait Dimensions: ‎18.9 x 28.4 x 2.5cm Wi-Fi: Yes Remote: No Built-in storage: 32GB Video: Yes USB/SD slots: Yes/Yes Cloud services: Frameo Today's Best Deals View at Amazon View at Amazon View at Amazon View at Amazon Reasons to buy + Crisp, clear, 2K 100% sRGB display + Huge 32GB storage holds 40,000 pics + Easy to share images with multiple users Reasons to avoid - App limits number of images and length of videos without subscription - Uploading from a computer is a faff - 5:3 aspect ratio not native to phones or cameras Buy it if ✅ You want a hi-res display: packs 2.4MP into its 11-inch screen for super-crisp detail with 100% Adobe sRGB color gamut ✅ You want easy sharing: ideal if you have a big extended family or trustworthy friends and need plenty of storage for images Don't buy it if ❌ You want to use a computer: while it's easy to upload images from a phone, it's much more of a faff from a Mac or PC ❌ Money is tight: there are cheaper alternatives though they're not nearly as nice There's a lot to like about the Lexar Pexar 11in digital photo frame. Perhaps the most important aspect of such a device is the quality of its screen, and this is an absolute cracker; packing 2.4 megapixels into 11 inches of real estate displays your images in beautifully crisp detail, while the full 100% sRGB color gamut ensures they are wonderfully vibrant too. The 32GB storage should be enough for pretty much everyone and is oodles more than most other frames on the market, ensuring enough storage space for even the most trigger-happy photographer. But if that's still not enough, then SD card and USB-A and USB-C slots enable up to 1TB of storage. The frame is Wi-Fi enabled, and it's a breeze for family members to share their shots via the Frameo app, no matter where they are in the world. There's no provision to upload files from a computer wirelessly though – you'll have to do it the old-fashioned way using a USB memory drive. It's very well priced considering its feature set. Be aware that there's a choice of two models, the other having a marginally smaller 10.1-inch screen but at a much lower-res 1.02 megapixels. The price difference is minimal though, and I'd go for the 11-inch version every day of the week. Read our full Lexar Pexar 11in photo frame review Swipe to scroll horizontally Quality It's a nice-looking frame if minimalism is your thing 4 / 5 Features Great 2K display, 100% sRGB color gamut and ginormous 32GB of storage 5 / 5 Value A well-specced frame for the price, but keep an eye for discounted deals 5 / 5 Today's best pexar deals $169.99 $139.99 View $199.99 $139.99 View $179.99 View Show more We check over 250 million products every day for the best prices Back to the top ⤴ Best widescreen photo frame (Image credit: Future) 4. Lexar Starlight 15.6in This widescreen frame's rear backlight really makes images shine Our expert review: Specifications Resolution: 1920 x 1080 Display: 15.6in touchscreen Orientation: Landscape and portrait Dimensions: 18 x 26 x 2.5cm (7.1 x 10.2 x 1in) Wi-Fi: Yes Remote: No Built-in storage: 64GB Video: Yes USB/SD slots: Yes/Yes Cloud services: Frameo Today's Best Deals View at Amazon View at Amazon Reasons to buy + Eye-catching backlit Gallery Lighting feature + Massive 64GB memory holds 80,000+ photos + Large 15.6in widescreen display Reasons to avoid - 16:9 aspect ratio crops both phone and camera images - On the pricey side Buy it if ✅ You want to show off shots in style: the Gallery Lighting features lifts the entire frame from its surroundings, and the 15.6in display is eye-catching ✅ You have a lot of photos: a supremely generous 64GB memory is enough to store in excess of 80,000 images Don't buy it if ❌ You don't want to crop: while the 16:9 ratio sets this apart, it's not native to phones or mirrorless cameras ❌ You're on a tight budget: it's one of the more expensive frames on the market The Pexar Starlight 15.6in digital photo frame distinguishes itself from the rest with a large widescreen display and a unique ambient backlight. The 15.6-inch anti-glare touchscreen has a 1920 x 1080 resolution with a 16:9 aspect ratio, displaying photographs with good clarity and brightness. Its standout Gallery Lighting feature casts a warm golden glow on the wall behind the frame, creating a sophisticated, floating effect. The frame itself has a wood-effect finish, offering a refreshing departure from standard black plastic bezels. A sturdy metal stand supports both portrait and landscape orientations, with auto-rotation functionality. It can also be hung on a wall with the supplied kit. Powered by the popular Frameo app, setup and photo sharing are easy-peasy. Images can be transferred to its massive 64GB of internal storage via Wi-Fi, SD card, or USB, and with space for approximately 80,000 photos, that's more than enough for anyone. However, the 16:9 aspect ratio means standard 4:3 photos from smartphones will be cropped. The Pexar Starlight is an upmarket choice for those who value aesthetics. Its large size and ambient lighting make it a centerpiece in any room. However, there's a premium price to be paid for its unique design elements. Read our full Pexar Starlight 15.6in digital photo frame review Swipe to scroll horizontally Quality The wood-effect surround is refreshing, and the touchscreen works well 4 / 5 Features It's a big display with enough storage for 80,000 photos, and the glowing surround is stunning 5 / 5 Value One of the more expensive digital photo frames, but you are paying for lovely quality 4 / 5 Today's best Pexar Starlight 15.6-inch deals $349.99 $299.99 View $349.99 $299.99 View We check over 250 million products every day for the best prices Back to the top ⤴ Best photo frame for smart homes (Image credit: Future) 5. Google Nest Hub <span class | 2026-01-13T09:29:41 |
https://support.atlassian.com/jira-software-cloud/docs/what-is-the-program-board-in-my-plan | What is the Program board in my plan? | Jira Cloud | Atlassian Support Skip to main content Jira Cloud Support Apps Documentation Resources Contact us Sign in Sign in Jira Software Cloud Documentation Set up Jira Cloud Learn how Jira products work What is the Jira family of apps? Get started with Jira Cloud Administer Jira Cloud Use Jira Cloud on Apple and Android devices Get help with Jira Cloud Access a space Use Jira Cloud with other Atlassian apps How to add new Atlassian apps from Jira Use Jira Cloud with Bitbucket Use Jira Cloud with Confluence Use Jira Cloud with other apps Configure development tools Configure collaboration tools Integrate Jira Cloud and Slack Integrate Jira Cloud with Microsoft Teams Integrate the Jira Cloud plugin for Copilot in Microsoft Teams Use Jira Cloud for Sheets What is the space toolchain in Jira? Integrate Jira Cloud with Gmail Automate what build and deployment events are sent from Jenkins to Jira Import data into Jira Prepare a CSV file for import Use a configuration file for space imports Import data to Jira using a CSV file Map CSV data to Jira fields Map column data to work types Import data directly from Asana into Jira Import data directly from Trello into Jira Import data directly from ClickUp into Jira Import data directly from monday into Jira Fix errors in a space import Import data from a business space to a software space Import data from a software space to a business space Import issues into an existing space in Jira using CSV Quick space creation with bundles See how teams use Jira How legal teams use Jira space templates How to use Jira for process management Use business spaces for project management Use business spaces for task management Use Jira business projects for finance projects Use Jira business projects for marketing projects Use Jira for HR projects Use Jira for operations spaces Use Jira for sales teams Manage Jira Cloud spaces Start a new software space for your team What is a Jira space? Create a new space What are the space templates? Edit a space's details What is a board in software spaces? Create a scrum board based on spaces What are Jira workflows? Switch between spaces and boards Copy an existing board Create a board based on filters Create a Kanban board based on spaces Example JQL queries for board filters Add users to space roles in your space Learn how company-managed and team-managed spaces differ What are team-managed and company-managed spaces? Migrate between team-managed and company-managed spaces How do features differ based on the type of space? How do work types differ based on space type? How do settings differ based on space type? Configure a company-managed board What are board filters? Enable ranking Configure columns Use the simplified workflow Configure quick filters Customize cards Configure how your board estimates and tracks work Configure the work item details Change the location of a board Add a sub-filter to a company-managed kanban board Can I use custom fields to track progress of my project? Change board filters for a company-managed board Configure swimlanes Configure working days Customize your view of the board and backlog Edit a board filter on a company-managed board How can I track work progress in Jira? Work item limits in company-managed spaces Show or hide work items on your board with quick filters What are story points? What are Time estimates (days, hours, minutes)? What is estimation in Jira? What is work item count? What is a simplified Jira workflow? Create and plan work with Scrum and Kanban Use your scrum backlog Use your kanban backlog What is a version? Configure versions in a scrum space Configure versions in a kanban space Manage epics in a scrum space Manage epics in a kanban space Monitor work in a kanban space Link a Confluence page to an epic What is an epic? Coordinate and monitor work with sprints What is a sprint? Use active sprints Create sprints in company-managed spaces Start a sprint in company-managed spaces What are parallel sprints? Enable parallel sprints Monitor the progress of a sprint Edit a sprint in a company-managed space Move or transition work items in an active sprint Reorder a sprint in a company-managed space Remove or delete work items from an active sprint Add work items to an active sprint View and edit work item details in an active sprint Link a Confluence page to a sprint Complete a sprint Complete parallel sprints Delete a sprint Delete a completed sprint in a company-managed space Reopen a sprint Group and track work with components What are Jira components? What are Compass components? Switch between Jira and Compass components Configure Jira components Configure Compass components Link work items to Jira components Link work items to Compass components View a space's components Release your team's work in versions Check the progress of a version Use the release page to check the progress of a version Check the release status of a version Create a version Release a version Track and analyze your team's work with reports Generate a report View and understand the burndown chart View and understand the Burnup chart or report View and understand the control chart Methods of calculating rolling average on the control chart View and understand the cumulative flow diagram View and understand the epic burndown report View and understand the epic report View and understand the velocity chart View and understand the version report View and understand the sprint report Strategies to reduce your cycle time Plan effectively with your deployment frequency report What is the release burndown report? Manage and visualize your software space on the timeline How do I view my software space's timeline? What does the space timeline show? Timeline limits in Jira What are filters on the timeline? Create work items on the timeline Schedule parent work items on your timeline Schedule work for kanban teams on your timeline Schedule work for scrum teams on your timeline Enable planning for child work items on the timeline Roll up dates on your timeline How can I plan with releases on my software space's timeline? Show or hide releases on your software space's timeline What are dependencies on the timeline? Show or hide dependencies on your timeline Create or remove dependencies on your timeline What does the progress bar on my timeline show? Enable or disable progress monitor in the timeline Change color of work item schedule bars on your timeline Change how many completed work items show on your software space's timeline Share a screenshot of your timeline Add your timeline to a Confluence Cloud page Enable and disable the timeline Troubleshoot the timeline for company-managed spaces Troubleshoot the timeline for team-managed spaces Delete a work item from the timeline How can I change my timeline view? View insights in Jira Cloud Understand backlog insights in company-managed spaces Understand insights on the board in company-managed spaces Configure insight settings in a company-managed space Manage insights in a company-managed project Manage and update work in a list What is the list? How do I view my list? Create and edit work items in your list Delete a work item from your list Customize your list by adding or removing fields Manage multiple work items in your list Link and unlink goals to work items in your Jira list Organize your list Filter, sort, copy, and rank work items in the list Schedule and track work in the calendar view What is the calendar? Schedule work in your calendar Configure your calendar Manage work items in your calendar Add the due date field to your work items Manage sprints in your calendar Manage releases in your calendar Protect your team’s data Set a default classification level for work items View and change a work item’s security level Add people to Jira from Google, Slack, or Microsoft Delete a space How to create workflows for business projects Manage and customize the space navigation Set up approvals in Jira What are approvals? Set up approval steps Work in Jira Cloud spaces Create and configure your work items What is a work item? Create a work item and a subtask Create work items using the CSV importer Add files, images, and other content to describe a work item Use Rovo to help write or edit content Create, edit, and delete work items on the board View a work item Update a work item's details Configure field layout in the work item Copy a work item layout to other spaces Customize the child work item table Choose when subtasks and linked work items have a strikethrough Work on and progress your work items Log time on a work item Estimate a work item Pin a field to the top of a work item Markdown and keyboard shortcuts Flag a work item Rank a work item Schedule a work item Transition a work item Link work items Clone a work item Watch, share and comment on a Jira work item Add an attachment to a work item Delete an attachment in a work item Use custom emojis to help describe a work item Download all attachments in the attachments panel Switch between the strip and list view for attachments Download an attachment from a work item Delete all attachments in the attachments panel Find a field on the work item Date and time formats in different languages Insert an attachment already on a work item Automatically assign work items to people Archive a work item Classify a work item Collaborate in real-time Comment on work item action Edit work items via the more actions menu in the backlog How redaction works Link work to goals on a work item Navigate work items in a list with your keyboard Smart Links in Jira View content in a side panel Transition work items through a workflow What are the different types of activity on a work item? Run a standup meeting in Jira Update multiple work items at once Edit multiple work items Change the status of multiple work items Move multiple work items Change the work type for multiple work items Delete multiple work items Watch multiple work items Integrate your work items and development tools Link repositories to a software space Link your project with Opsgenie Process work items with smart commits Reference work items in your development spaces View development information for a work item View release information for a work item Work with dashboards in Jira Cloud What is a Jira dashboard? Create and edit dashboards Search for an existing or shared dashboard Add and customize gadgets Set up a wallboard Share Jira dashboards in Confluence Manage your user profile View and update your profile Allow OAuth access Manage your Jira personal settings Learn about changes coming to your Jira Cloud experience Upcoming changes: Epic link data above the epic level Upcoming changes: 'epic-link' replaced with 'parent' Confluence signup from Jira Connect Cisco to Jira Connect Jira Service Management services to Jira Software Integrate work with Atlassian Home Link work in Jira to goals and projects in Atlassian Home Understand how Jira works with goals and projects in Atlassian Home Navigate Jira with your keyboard What is the command palette? Search work items, projects, and more with your keyboard Change the status of a work item with your keyboard Move a work item with your keyboard Delete a work item with your keyboard Add a child work item with your keyboard Edit the parent of a work item with your keyboard Edit the assignee of a work item with your keyboard Edit the story point estimate of a work item with your keyboard Edit the sprint of a work item with your keyboard Edit the due date of a work item with your keyboard Edit labels of a work item with your keyboard Edit components of a work item with your keyboard Edit fix versions of a work item with your keyboard Edit the priority of a work item with your keyboard Link and unlink a work item with your keyboard Use keyboard shortcuts View your work suggestions in Jira Work with incidents in Jira What is the incidents feature? Connect an incident management tool to Jira Manage incidents in Jira Connect and remove services in Jira Connect New Relic to Jira Work with security vulnerabilities in Jira Connect or remove security containers in Jira Link security vulnerabilities to Jira work items Work with development in Jira Cloud What is development in Jira Cloud? Key metrics on the Development page Work suggestions on the Development page Related work on the Development page Enable the development feature Add custom fields to your space Collect information for your team with forms What are forms and what can they do? How to create, edit, save, and delete forms Add or remove fields from your form Manage access and share a form Customize your form fields Conditionally show form fields How secure are public forms? Create a chart showing data from your work items Get started in Jira business spaces What are Jira business spaces? What is a board in business spaces? Highlight work items from your list Create a format rule Delete a format rule Edit a format rule Manage multiple format rules What are format rules? Organize your board Share a Jira board or backlog in Confluence Share a Jira release in Confluence Use custom space templates Create a custom space template Use a custom template to create a new space Use Loom in Jira Cloud Use smart replies in work item comments What is the summary view? Work in Jira business spaces Change your space background Filter work items Categorize work items in the list view Work with boards in business spaces Customize cards on your business space's board Add, edit, or delete a shortcut What are approvals in business spaces? Sign off and approve work How to manage approvers Add, rename, or delete a column in team-managed business spaces Create a business space Edit and reorder work items on the timeline Save your filters in business spaces Set up approvals in your business space Show software releases in a business team calendar Troubleshoot approvals in business projects View all attachments in a business project View and manage versions in business projects What is the timeline view and how do I use it? Workflows and statuses for boards in business projects Work in Jira Cloud team-managed spaces Get started with team-managed spaces Add your team to team-managed boards Enable agile features in team-managed spaces Enable the backlog Enable sprints Enable estimation Enable and disable Confluence pages in Jira Enable releases and versions Enable code Enable reports Enable deployments Enable on-call schedules Specify a date range for your deployments View and understand your cycle time report View and understand your deployment frequency report View and understand your deployment insights What is the burnup report? What is the cumulative flow diagram? What is the sprint burndown report? What is the velocity report? Manage and administer team-managed spaces Create and edit team-managed spaces Add people to team-managed spaces Manage how people access your team-managed space Team-managed space permissions Set up work types in team-managed spaces Customize work item fields in team-managed spaces Available custom fields for team-managed spaces Manage epics in team-managed spaces Manage subtasks in team-managed spaces Manage filters in team-managed spaces Add rules to your team-managed board Team-managed board rules Customize notifications in team-managed spaces Connect your team-managed board with Bitbucket Manage Atlassian Marketplace apps in team-managed spaces Restrict access to a work type Work item limits in team-managed spaces Manage how work flows in your team-managed space Create, edit and delete statuses in team-managed spaces Manage work item transitions in team-managed spaces Add or remove workflow rules in team-managed spaces Available workflow rules in team-managed spaces Create and edit multiple workflows in team-managed projects Best practices for workflows in Jira Group workflow rules to further restrict your transitions Map a workflow with your team Move work items to new statuses while updating your workflow Set up a workflow in a team-managed software space What are the different workflow rule types? Configure columns and statuses in your team-managed sapce Assign statuses and edit columns in a team-managed space Manage columns and statuses in team-managed software spaces View and understand insights in team-managed spaces Understand insights on the backlog in team-managed projects Understand insights on the board in a team-managed project Configure insight settings in a team-managed project Search for work items in Jira Search and find your work items Find recent work items Find specific work items Search for work items in a project Search for work items using the text field Navigate to your work Use Rovo to search for work items What is the new Jira work item search experience? What is the new navigation in Jira? What is the new navigation in Jira Service Management? Use advanced search with Jira Query Language (JQL) What is advanced search in Jira Cloud? JQL functions JQL fields JQL keywords JQL operators JQL developer status JQL design search JQL vulnerability search Search for custom fields from plans in JQL JQL optimization recommendations Save your search as a filter What is a saved search? Manage filters Work with search results Change the view of search results Edit individual and multiple work items Export search results Manage search results Edit multiple issues at the same time Plan and view work across multiple spaces in a plan Get started with plans What are plans in Jira Premium? Where do I find plans? Common configurations for Jira administrators before using Plans View a sample plan Create a new plan How do I navigate my plan? What settings can you change in your plan? How your plan shows work items on your timeline What do the symbols in your plan mean? What keyboard shortcuts are available in your plan? Add teams and releases to your plan Build out your plan Planning tools in plans Create different views of your plan How Ted uses Plans for scenarios and capacity How Veronica uses Plans for cross-space planning Configure Jira for plans Configure custom hierarchy levels in your plan Configure Dependencies in Jira for your plan Change financial year dates in your plans Manage inherited permissions in plans Set up your plan and change its settings Add or remove fields from your plan Change the date field used to schedule work items in your plan View and change the scope of work in your plan Remove work items from your plan using rules Change plan information and who can access it Types of permissions in your plan Remove individual work items from your plan Change how your plan handles dependencies in the same iteration Change how work is estimated in your plan How your plan handles timezones Configure the auto-scheduler in your plan Delete or archive your plan Duplicate your plan Performance recommendations for your plan Limitations of team-managed spaces in your plan Limits on plan size Manage and edit work items in your plans Create a work item in your plan Link work item to a parent in your plan What is work item ranking in your plan? Assign a work item to a team in your plan How your plan handles completed and resolved work items Edit multiple work items in bulk on your plan Track progress using estimates in your plan Track progress using work item count in your plan Troubleshoot missing work items in your plan Estimate and schedule work items in your plans Schedule work items in your plan according to sprints Schedule work items in your plan using start/end dates Schedule work items in your plan according to releases What are roll-ups in my plan? How your plan rolls up dates How your plan rolls up estimates What are partial rollups in your plan? Sprint states in your plan What are external sprints in your plan? Autoschedule work items on your plan How does the auto-scheduler in my plan work? Plan your next quarter using a Program board What is the Program board in my plan? What does the Program board show? Recommended preparations before using the Program board Create a new Program board in your plan Schedule work items from the Program board in your plan Add and change sprints on the Program board in your plan View and manage dependencies on the Program board Change work item info from the Program board in your plan Update and remove Program boards in your plan Create different planning scenarios in your plans What are scenarios in my plan? Turn scenarios on or off in your plan Create a scenario in your plan Rename, edit, and delete scenarios in your plan Manage capacity in your plans What are capacity and velocity in your plan? Enable capacity planning in your plan How your plan assigns capacity Capacity in scrum vs. kanban teams in your plan Change iteration capacity from your plan Monitor capacity and sprints in your plan Manage releases in your plans What are releases in your plan? Turn releases in your plan on or off View and edit releases in your plan Create a single-space release in your plan Create a cross-space release in your plan How do single-space and cross-space releases differ? Align cross-space release dates in your plan Track releases in your plan Remove releases in your plan Manage teams in your plan How do I use teams in plans? Create a new team from your plan Make a plan-only team an Atlassian team in your plan View and edit teams in your plan Remove and delete teams from your plan Add an Atlassian team to your plan Associate a team to a work source in your plan Edit a team’s information in your plan Limitations of teams in open planning sites View and manage dependencies in your plans What are dependencies in your plan? Add a dependency in your plan View a specific dependency on your plan View all of a work item's dependencies on your plan Change how your plan timeline displays dependencies Remove a dependency in your plan What is the dependencies view in your plan? Refine the dependencies view of your plan Resolve warnings in your plans Troubleshoot warnings on your timeline in your plan What are warnings in your plan? Change how your plan displays your data What is the summary view of your plan? What is the calendar view of your plan? What is the list in your plan? Show or hide columns in your plan timeline Filter work items on your plan Add color to work items in your plan Group work items on your plan Search for a specific work item on your plan Change how your plan sorts your work items How your plan sorts work items Preconfigured views in your plan Manage and delete timeline views in your plan Save a new view in your plan Show full hierarchy while filtering issues on your plan Change what shows on the Calendar view of your plan Change what the Program board in your plan shows Review and save changes made in your plans Save changes made in a plan Filter changes made in your plan Troubleshoot warnings in Unsaved changes modal Abandon a save in your plan Share and export your plan Share and embed your plan in Atlassian apps Export your plan data as .csv Create a static image of your plan Embed your plan using an iFrame Atlassian Support Jira Software Resources Plan and view work across multiple spaces in a plan Plan your next quarter using a Program board Cloud Data Center What is the Program board in my plan? This page refers to the advanced planning features that are only available as part of Jira Cloud Premium and Enterprise. The Program board interface gives planners visibility into the work, priorities, and dependencies of multiple teams so they can plan for multiple iterations at once. It can be used by all planners, but it’s been optimized to support Program Increment Planning rituals (also called Program planning or Quarterly planning), which are an essential part of the SAFe planning methodology. Want to see the Program board in action? Watch a video tutorial of how to set up and use the Program board in Plans . This view focuses on work items at the level 1 and level 0 hierarchy levels (commonly referred to as the Epic and Story levels). Any hierarchy levels above or below these – such as Initiative or Subtasks – won’t show on this view. Read more about hierarchy levels in Jira . Each plan can have two active program boards at any time. A Program board is considered active if its end date is in the future. Once a Program board’s end date passes, the board is completed and no longer counts against your allotment of active boards. The Program Board isn’t designed for real-time collaborative planning sessions such as Big Room Planning. For now, we recommend using a whiteboarding tool alongside the Program board to accommodate the large number of inputs needed for a collaborative planning session. To get started with your Program board, select Program from the left side navigation then select Create program board . See what the Program board shows . Was this helpful? Yes No It wasn't accurate It wasn't clear It wasn't relevant Provide feedback about this article Still need help? The Atlassian Community is here for you. Ask the Community Plan your next quarter using a Program board What is the Program board in my plan? What does the Program board show? Recommended preparations before using the Program board Create a new Program board in your plan Schedule work items from the Program board in your plan Show more Community Questions, discussions, and articles Accessibility Notice at Collection Privacy Policy Terms of Use Security 2026 Atlassian | 2026-01-13T09:29:41 |
https://trello.com/de/home#skip-target | Erfasse, organisiere und erledige deine Aufgaben von überall aus | Trello Weiter zum Hauptinhalt Funktionen Lösungen Tarife Preise Ressourcen Entdecke die Features, die deinem Team zum Erfolg verhelfen Eingang Erfasse alle wichtigen Details aus E-Mails, Slack und mehr direkt in deinem Trello-Posteingang. Planer Synchronisiere deinen Kalender und weise Zeitfenster für konzentriertes Arbeiten zu, um die Produktivität zu steigern. Automatisierung Automatisiere Aufgaben und Workflows mit Trello. Power-Ups Power-Up für deine Teams: Verknüpfe ihre Lieblingstools mit Trello-Plugins! Vorlagen Gib deinem Team eine Blaupause für den Erfolg mit benutzerfreundlichen Vorlagen von branchenführenden Unternehmen und der Trello-Community. Integrationen Finde Apps, die dein Team bereits nutzt, oder entdecke neue Möglichkeiten, um deine Arbeit in Trello zu erledigen. Lerne Trello kennen Trello hilft deinem Team bei der Arbeit. Unabhängig vom Projekt, Workflow oder Team – mit Trello kannst du alles organisieren. Es ist ganz einfach! Registriere dich, erstelle ein Board und schon kann es losgehen. Trello kennenlernen Unsere Trello-Playbooks eignen sich für Teams aller Art – lass dich inspirieren! Marketingteams Egal, ob es um die Produkteinführung, eine Kampagne oder die Erstellung neuer Inhalte geht – Trello verhilft Marketingteams zum Erfolg. Produktmanagement Verwende die Management-Boards und Roadmap-Funktionen von Trello, um komplexe Projekte und Prozesse zu vereinfachen. Engineering-Teams Mit Trello kannst du schneller mehr Code liefern und die Agilität deines Entwicklerteams verbessern. Designteams Unterstütze deine Designteams mit Trello, um kreative Anfragen und die teamübergreifende Zusammenarbeit zu verbessern. Start-ups Vom Erreichen der Umsatzziele bis hin zur Verwaltung von Workflows – kleine Unternehmen profitieren von Trello. Remote-Teams Sorge dafür, dass dein Remote-Team in Verbindung und motiviert bleibt, egal, wo auf der Welt sich deine Mitarbeiter befinden. Alle Teams anzeigen Unser Produkt in der Praxis Anwendungsbeispiel: Aufgabenmanagement Aufgabenverfolgung mit dem gewissen Etwas – überwache den Fortschritt deiner Aufgaben zentral in einer praktischen Ansicht. Anwendungsfall: zentrale Ressourcenverwaltung Spart euch jede Menge Zeit, indem deine Teams benötigte Informationen schnell und einfach an einem zentralen Ort finden. Anwendungsbeispiel: Projektmanagement Mit Trello kannst du Projekte organisieren, Fristen einhalten und Teamkollegen auf dem Laufenden halten. Alle Anwendungsbeispiele anzeigen Standard Für Teams, die mehr Aufgaben managen und die Zusammenarbeit skalieren müssen. Premium Ideal für Teams mit bis zu 100 Personen, die mehrere Projekte verfolgen und ihre Aufgaben auf unterschiedliche Weise visualisieren müssen. Enterprise Alles, was deine Enterprise-Teams und -Admins für das Projektmanagement brauchen. Free-Tarif Für Einzelpersonen oder kleine Teams, die ihre Aufgaben organisieren möchten. Trello entdecken Tarife und Preise vergleichen Egal, ob sich dein Team aus 2 oder 2.000 Personen zusammensetzt: Mit den flexiblen Preismodellen von Trello zahlst du nur für das, was du auch wirklich brauchst. Trello-Preisliste anzeigen Lernen und austauschen Trello-Leitfaden Unser einfacher Workflow-Leitfaden unterstützt dich bei der Projekteinrichtung und macht dich in Nullkommanichts zum Trello-Experten! Leitfaden für die Remote-Arbeit Ein umfassender Leitfaden zum Aufbau erfolgreicher Remote-Teams Webinare Sieh dir unsere kostenlosen Trello-Webinare an und werde ein Produktivitätsprofi. Kundenberichte Erfahre aus erster Hand, wie Unternehmen Trello als wichtigen Teil ihres Workflows einsetzen. Entwickler Dieses Power-Up bietet dir unzählige Möglichkeiten, Trello-Benutzern genau das zu liefern, was sie brauchen. Hilfreiche Ressourcen Benötigst du Hilfe? Unsere Artikel und FAQs helfen dir weiter. Zurück Navigation Funktionen Lösungen Tarife Preise Ressourcen Entdecke die Features, die deinem Team zum Erfolg verhelfen Eingang Erfasse alle wichtigen Details aus E-Mails, Slack und mehr direkt in deinem Trello-Posteingang. Planer Synchronisiere deinen Kalender und weise Zeitfenster für konzentriertes Arbeiten zu, um die Produktivität zu steigern. Automatisierung Automatisiere Aufgaben und Workflows mit Trello. Power-Ups Power-Up für deine Teams: Verknüpfe ihre Lieblingstools mit Trello-Plugins! Vorlagen Gib deinem Team eine Blaupause für den Erfolg mit benutzerfreundlichen Vorlagen von branchenführenden Unternehmen und der Trello-Community. Integrationen Finde Apps, die dein Team bereits nutzt, oder entdecke neue Möglichkeiten, um deine Arbeit in Trello zu erledigen. Lerne Trello kennen Trello hilft deinem Team bei der Arbeit. Unabhängig vom Projekt, Workflow oder Team – mit Trello kannst du alles organisieren. Es ist ganz einfach! Registriere dich, erstelle ein Board und schon kann es losgehen. Trello kennenlernen Unsere Trello-Playbooks eignen sich für Teams aller Art – lass dich inspirieren! Marketingteams Egal, ob es um die Produkteinführung, eine Kampagne oder die Erstellung neuer Inhalte geht – Trello verhilft Marketingteams zum Erfolg. Produktmanagement Verwende die Management-Boards und Roadmap-Funktionen von Trello, um komplexe Projekte und Prozesse zu vereinfachen. Engineering-Teams Mit Trello kannst du schneller mehr Code liefern und die Agilität deines Entwicklerteams verbessern. Designteams Unterstütze deine Designteams mit Trello, um kreative Anfragen und die teamübergreifende Zusammenarbeit zu verbessern. Start-ups Vom Erreichen der Umsatzziele bis hin zur Verwaltung von Workflows – kleine Unternehmen profitieren von Trello. Remote-Teams Sorge dafür, dass dein Remote-Team in Verbindung und motiviert bleibt, egal, wo auf der Welt sich deine Mitarbeiter befinden. Alle Teams anzeigen Unser Produkt in der Praxis Lies dir unsere Anwendungsbeispiele durch, um Trello in deinem Team optimal zu nutzen. Alle Anwendungsbeispiele anzeigen Standard Für Teams, die mehr Aufgaben managen und die Zusammenarbeit skalieren müssen. Premium Ideal für Teams mit bis zu 100 Personen, die mehrere Projekte verfolgen und ihre Aufgaben auf unterschiedliche Weise visualisieren müssen. Enterprise Alles, was deine Enterprise-Teams und -Admins für das Projektmanagement brauchen. Free-Tarif Für Einzelpersonen oder kleine Teams, die ihre Aufgaben organisieren möchten. Trello entdecken Tarife und Preise vergleichen Egal, ob sich dein Team aus 2 oder 2.000 Personen zusammensetzt: Mit den flexiblen Preismodellen von Trello zahlst du nur für das, was du auch wirklich brauchst. Trello-Preisliste anzeigen Lernen und austauschen Trello-Leitfaden Unser einfacher Workflow-Leitfaden unterstützt dich bei der Projekteinrichtung und macht dich in Nullkommanichts zum Trello-Experten! Leitfaden für die Remote-Arbeit Ein umfassender Leitfaden zum Aufbau erfolgreicher Remote-Teams Webinare Sieh dir unsere kostenlosen Trello-Webinare an und werde ein Produktivitätsprofi. Kundenberichte Erfahre aus erster Hand, wie Unternehmen Trello als wichtigen Teil ihres Workflows einsetzen. Entwickler Dieses Power-Up bietet dir unzählige Möglichkeiten, Trello-Benutzern genau das zu liefern, was sie brauchen. Hilfreiche Ressourcen Benötigst du Hilfe? Unsere Artikel und FAQs helfen dir weiter. Bessere Zusammenarbeit im Team Entdecke Trello-Anwendungsbeispiele, Produktivitätstipps, Best Practices für die Teamzusammenarbeit und Expertentipps für die Remote-Arbeit. Trello-Blog ansehen Accelerate your teams' work with AI features 🤖 now available for all Premium and Enterprise! Learn more. Erfasse, organisiere und erledige deine Aufgaben von überall aus. Entfliehe der Unordnung und dem Chaos und entfessele deine Produktivität mit Trello. Jetzt registrieren – es ist kostenlos! Durch Eingabe meiner E-Mail-Adresse erkenne ich die Datenschutzrichtlinie von Atlassian an. Video ansehen Hero Trello 1x1 Produktivität ohne Kompromisse Arbeite mit Posteingang, Boards und Planer organisiert und effizient. Jede Aufgabe, Idee oder Verpflichtung, sei sie auch noch so klein, findet ihren Platz, sodass du immer auf dem neuesten Stand bist. Eingang Vom Einfall direkt zum Element im Posteingang: Erfasse deine Aufgaben überall und jederzeit. Boards Eine lange Aufgabenliste ist eine Herausforderung, die sich meistern lässt. Behalte alles von Anfang bis Ende im Blick. Planer Ziehen, ablegen, erledigen: Trage deine wichtigsten Aufgaben in deinen Kalender ein und reserviere Zeit für das, was wirklich wichtig ist. Eingang Vom Einfall direkt zum Element im Posteingang: Erfasse deine Aufgaben überall und jederzeit. Boards Eine lange Aufgabenliste ist eine Herausforderung, die sich meistern lässt. Behalte alles von Anfang bis Ende im Blick. Planer Ziehen, ablegen, erledigen: Trage deine wichtigsten Aufgaben in deinen Kalender ein und reserviere Zeit für das, was wirklich wichtig ist. Von der Nachricht zur Aktion Wandele Nachrichten aus deinen bevorzugten Apps schnell in Aufgaben um und organisiere all deine Diskussionen und Aufgaben am selben Ort. E-MAIL-MAGIE Verwandele deine E-Mails ganz einfach in Aufgaben. Du musst sie dazu nur an deinen Trello-Posteingang weiterleiten, wo sie von Atlassian Intelligence (AI) in organisierte Aufgaben mit allen erforderlichen Links umgewandelt werden. SPEZIELLE FUNKTIONEN FÜR MESSAGING-APPS Du musst auf eine Nachricht aus Slack oder Microsoft Teams reagieren? Sende sie einfach direkt an dein Trello-Board. Über die Benutzeroberfläche deiner bevorzugten App kannst du Nachrichten aus deinem Trello-Posteingang mit KI-generierten Zusammenfassungen und Links speichern. Sorge für eine intelligente Arbeitsweise Erledige mehr mit Trello Nutze unkomplizierte Integrationen, Automatisierung und Spiegelung deiner Aufgaben an mehreren Standorten für eine individuelle Organisation. Integrationen Binde Apps, mit denen du bereits arbeitest, in deinen Trello-Workflow ein, oder füge ein Power-Up hinzu, um eine bestimmte Aufgabe zu erfüllen. Integrationen durchsuchen Automatisierung Jedes Trello-Board bietet eine integrierte Automatisierung ohne Code. Konzentriere dich auf die wirklich wichtige Arbeit, während die Roboter den Rest erledigen. Lerne die Automatisierung kennen Kartenspiegelung Zeige all deine Aufgaben von verschiedenen Boards an einer zentralen Stelle an. Du kannst Karten spiegeln, um deine Aufgaben dort im Blick zu behalten, wo du gerade arbeitest. Tarife vergleichen [Trello ist] großartig, um komplexe Prozesse zu vereinfachen. Als Manager kann ich [Prozesse] in mundgerechte Stücke für mein Team zerlegen und diese dann delegieren, aber immer noch den Überblick behalten. Joey Rosenberg Global Leadership Director bei Women Who Code Story lesen 75 % der Organisationen geben an, dass Trello innerhalb von 30 Tagen einen Mehrwert für ihr Unternehmen liefert. Trello TechValidate-Umfrage Egal, ob im Büro, von zu Hause aus oder vor Ort mit einem Kunden gearbeitet wird: Kontext und Informationen können über Trello geteilt werden. Sumeet Moghe Produktmanager bei ThoughtWorks Story lesen 81 % der Kunden entschieden sich für Trello wegen seiner Benutzerfreundlichkeit. Trello TechValidate-Umfrage Wir verwendeten Trello, um mehr Klarheit bezüglich der Schritte, Anforderungen und Verfahren zu schaffen. Das war außerordentlich, wenn man mit Teams kommunizierte, die sich hinsichtlich Kultur und Sprache deutlich unterscheiden. Jefferson Scomacao Entwicklungsmanager bei IKEA/PTC Story lesen 74 % der Kunden sagen, dass Trello die Kommunikation mit ihren Kollegen und Teams verbessert hat. Trello TechValidate-Umfrage Tritt einer Community aus Millionen von Benutzern weltweit bei, die für höhere Produktivität bereits auf Trello vertraut. Tritt einer Community aus Millionen von Benutzern weltweit bei, die für höhere Produktivität bereits auf Trello vertraut. Starte noch heute mit Trello durch Jetzt registrieren – es ist kostenlos! Durch Eingabe meiner E-Mail-Adresse erkenne ich die Datenschutzrichtlinie von Atlassian an. Anmelden Informationen zu Trello Was hinter den Boards steckt. Stellenangebote Informiere dich über offene Stellen im Trello-Team. Apps Lade die Trello-App auf deinen Computer oder dein Mobilgerät herunter. Kontakt Hast du eine Frage? Kontaktiere uns – wir helfen dir gern! Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Datenschutzrichtlinie Nutzungsbedingungen Copyright © 2023 Atlassian | 2026-01-13T09:29:41 |
https://lever.co/customers/ | Lever Success Stories: How Talent Teams Thrive with LeverTRM Sales: (888) 885.5299 Sign In Support Solutions AI Companions AI Interview Companion AI Screening Companion Solutions Recruitment Marketing High-Volume Hiring Diversity & Inclusion Hiring Recruitment Automation Recruitment Analytics Recruitment Communication Career Site Builder Solution Add Ons View All Check Out Our Product Guide See Product Guide Resources Learn Blog Hiring & Recruiting Resources Connect Events & Webinars 2025 Benchmarks Report Get the Report Company Company Why Lever What Customers Say Partner Integrations Careers Join our Team Request Demo Pricing What Our Customers Say Read our customer stories and Talent Relationship Management reviews. Read Our Customer Stories The power of our collective reach 0 K + Customers 0 M Active Jobs 0 M Candidates 0 .6M Avg Annual Hires 0 + Employees Refine Your Search Integrations How DREAM Charter Schools Build Authentic Teams Read the Story Analytics Lever Nurture How LeverTRM Supported Rapid Growth at Celerion Read the Story LeverTRM Insomnia Cookies Speeds Up Hiring Process with LeverTRM for Enterprise Read the Story Analytics LeverTRM How Entrata Scales Its Global Hiring with LeverTRM Read the Story Lever Nurture LeverTRM How Mastery Charter Schools Reduced Time to Hire 29% Read the Story LeverTRM LeverTRM Powers Global Hiring Growth for Mitek Systems Read the Story Award-Winning Recruiting Software Lever is rated a top HR software, leader in mid-market, and a highest satisfaction product.
Learn more about our ATS + CRM solution. Start Growing Your Company with Lever Learn how your company can deliver the best candidate experience,
improve quality of hire, and prove the value of talent acquisition to your business. See the Platform Contact Lever Solutions Applicant Tracking System AI Interview Companion AI Screening Companion Onboarding Recruitment Analytics Recruitment Automation Recruitment Marketing High-Volume Hiring All Solutions Explore Pricing Request a Demo Content Library Events Webinars Blog Partner Integrations Marketplace Compare & Choose Lever vs. Ashby Lever vs. Greenhouse Lever vs. Workable Lever vs. SmartRecruiters iCIMS vs. SmartRecruiters Greenhouse vs Ashby Greenhouse Alternatives Ashby Alternatives Company About Us Customers Careers Contact Us Support Help Center Product Status Support Connect with Us Privacy Policy Terms of Use Security © 2025 Employ Inc. All rights reserved. Employ, JazzHR, Lever, and Jobvite are registered trademarks of Employ, Inc. Terms and conditions, features, support, pricing, and service options subject to change without notice. | 2026-01-13T09:29:41 |
https://telegram.org/dl?tme=2523e158d11fd00d2b_2712743390112853009 | Telegram Applications English Bahasa Indonesia Bahasa Melayu Deutsch Español Français Italiano Nederlands O‘zbek Polski Português (Brasil) Türkçe Беларуская Русский Українська Қазақша العربية فارسی 한국어 Twitter Home FAQ Apps API Moderation Telegram Applications Telegram apps are open source and support reproducible builds . Anyone can independently verify that Telegram apps you download from App Store or Google Play were built using the exact same code that we publish. Mobile apps Telegram for Android Telegram for iPhone and iPad Desktop apps Telegram for Windows/Mac/Linux Telegram for macOS Web apps Telegram WebK Telegram WebA Telegram Database Library (TDLib) TDLib – a cross-platform client designed to facilitate creating custom apps on the Telegram platform. Telegram X for Android – a slick experimental Telegram client based on TDLib. Unofficial apps Unigram, a client optimized for Windows (based on TDLib ) Telegram CLI for Linux MadelineProto Source code This code allows security researchers to fully evaluate our end-to-end encryption implementation . It is also possible to independently verify that Telegram apps available on Google Play and App Store are built using the same code that we publish on GitHub. Telegram Database Library Cross-platform library for building custom Telegram apps, see TDLib for details. Licensed under Boost 1.0 . GitHub » Telegram for Android Official Android App, see Google Play Market page for full description. Licensed under GNU GPL v. 2 or later . GitHub » Download APK File » Telegram for iOS Licensed under GNU GPL v. 2 or later . GitHub » Telegram for macOS Native macOS client. Licensed under GNU GPL v. 2 . GitHub » Telegram for Web browsers Telegram Web, Version K . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Telegram Web, Version A . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Legacy JavaScript client . Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram React JavaScript client for browsers. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram Desktop Qt-based desktop client. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram for WP Licensed under GNU GPL v. 2 or later . GitHub » Telegram X for Android Alternative Telegram client for Android based on TDLib. Licensed under GPL v.3.0 GitHub » Unofficial apps Telegram CLI (Unofficial) Linux Command-line interface for Telegram. Licensed under GNU GPL v. 2 . GitHub » Unigram (Unofficial) A Telegram client optimized for Windows. Licensed under GNU GPL v. 3 or later . GitHub » MadelineProto (Unofficial) A PHP MTProto Telegram client. Licensed under GNU AGPL v. 3 . GitHub » Bug Bounty Program Telegram welcomes developers and the security research community to audit its services, code and protocol seeking vulnerabilities or security-related issues. Learn more about our Bug Bounty Program here . Telegram Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. About FAQ Privacy Press Mobile Apps iPhone/iPad Android Mobile Web Desktop Apps PC/Mac/Linux macOS Web-browser Platform API Translations Instant View About Blog Press Moderation | 2026-01-13T09:29:41 |
https://aws.amazon.com/products/storage/ | Cloud Storage Services on AWS Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account Products › Storage Cloud Storage on AWS Reliable, scalable, and secure storage for your data Maximize economic advantages by migrating to AWS Cloud Infrastructure Analyst firm, Enterprise Strategy Group, validated that organizations reduced compute, networking, and storage costs by up to 66% by migrating on-premises workloads to AWS Cloud Infrastructure. Read the report Why Cloud Storage on AWS? Millions of customers use AWS cloud storage services to transform their business, increase agility, reduce costs, and accelerate innovation. Choose from a broad portfolio of storage solutions with deep functionality for storing, accessing, protecting, and analyzing your data. Play Benefits of Cloud Storage on AWS Access the storage you need faster Make resources available in minutes, not weeks. Speed time to market, avoid complex capacity planning, and reduce over-provisioning with just a few clicks. Reduce storage spend Minimize your total cost of ownership (TCO) with managed services that eliminate infrastructure maintenance. Optimize your storage costs based on how frequently and quickly you need to access your data. Secure and protect your data Safeguard your data with unmatched security and storage designed for 99.999999999 (11 9s) of durability and multi Availability Zone resilience. Keep data available to your applications with data resilience provided through options from granular restore to recovery across AWS and on-premises environments. Fuel innovation with new insights Choose from a variety of tools to get more from your data and accelerate new product and service delivery. Run big data analytics, artificial intelligence (AI), machine learning (ML), high-performance computing (HPC), and media processing applications on all your cloud data. Build a data foundation for generative AI Enable generative AI with secure, scalable data lakes, high-performance storage for model training, and integration with AWS data services for generative AI to customize foundation model responses and differentiate applications with your data. AWS re:Invent 2024 Storage sessions on-demand Catch up with storage highlights from re:Invent View the full AWS Storage session playlist Play AWS Storage Services Filter by category Displaying 1-8 (11) Object storage Amazon Simple Storage Service (S3) Object storage with industry-leading scalability, availability, and security for you to store and retrieve any amount of data from anywhere. Learn more File storage Amazon Elastic File System (EFS) A simple, serverless, elastic, set-and-forget file system for you to share file data without managing storage. Learn more File storage Amazon FSx Fully managed, cost-effective file storage offering the capabilities and performance of popular commercial and open-source file systems. Learn more Block storage Amazon Elastic Block Store (EBS) Easy to use, high-performance block storage service for both throughput and transaction-intensive workloads at any scale. Learn more File storage Amazon File Cache High-speed cache for datasets stored anywhere, accelerate cloud bursting workloads. Learn more Data migration AWS DataSync Online data transfer service that optimizes network bandwidth and accelerates data movement between on-premises storage and AWS storage. Learn more Data migration AWS Snowball Edge compute, data collection, and data transfer with security and end-to-end logistics for mobile and rugged deployments. Learn more Hybrid cloud storage and edge computing AWS Storage Gateway Hybrid cloud storage service that gives you on-premises access to virtually unlimited cloud storage. Learn more Show all Use cases Migrate applications to AWS Lift and shift your existing workloads to AWS quickly using like-for-like storage for simple cloud migration. Move your network-attached storage (NAS), storage area network (SAN), and Hadoop workloads as-is with AWS services, and evolve at your own pace. Build data lakes Consolidate your data so it’s easier to model and analyze. Use Amazon S3 to build a secure, durable, and scalable data lake. Take advantage of its integration with a wide range of services for analytics and ML. Modernize application development Build cloud-native applications and get to market faster with a microservices architecture and more. Choose AWS storage services that persist and share data from your AWS containers and serverless applications. Backup to AWS storage Extend secondary storage targets to the cloud to address exponential data growth. Migrate copies of on-premises data to AWS and protect applications already in the cloud with services from AWS and AWS Partners. Archive to the cloud Meet long-term retention requirements with AWS storage services. Manage compliance and digital preservation with services that provide security, reliability, unlimited scalability, and 99.999999999% durability. Access data faster than on-premises tape. AWS Storage Blogs Read AWS Storage blogs for the latest technical guidance and best practices Explore blogs AWS Summit Hamburg 2025: Experience tomorrow's cloud today Join industry pioneers and cloud experts for a day of hands-on learning and networking opportunities that will transform your business's cloud journey. Register now Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:41 |
https://git-scm.com/book/bg/v2/Git-%d0%b8%d0%bd%d1%81%d1%82%d1%80%d1%83%d0%bc%d0%b5%d0%bd%d1%82%d0%b8-%d0%9f%d0%be%d0%b4%d0%bc%d0%be%d0%b4%d1%83%d0%bb%d0%b8 | Git - Подмодули About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 5.11 Git инструменти - Подмодули Подмодули Често се случва докато работите по един проект да трябва да използвате друг такъв в него. Може да е библиотека разработена от други или такава, която сте написали вие, но я използвате в множество проекти. В такива случаи възниква тривиален проблем: искате да третирате двата проекта като отделни, но и да можете да използвате единия в другия. Ето пример. Разработвате уебсайт и създавате Atom потоци. Вместо да пишете собствен Atom генериращ код, решавате да използвате библиотека. Може да вмъквате кода от споделени библиотеки като CPAN install или Ruby gem или да копирате сорса в дървото на собствения си проект. Проблемът с включването на библиотеката е, че е трудно да я настроите според вашите нужди и често е още по-трудно да я внедрите в production среда, защото трябва да сте сигурни, че всеки клиент я има при себе си. Проблемът с копирането във вашия проект пък е, че всички ваши промени по библиотеката ще станат трудни за сливане когато upstream източника се промени. Git се занимава с тези проблеми посредством подмодули. Подмодулите ви позволяват да пазите Git хранилище като поддиректория в друго Git хранилище. Това от своя страна ви позволява да клонирате друго хранилище във вашия проект и да пазите къмитите им изолирани. Първи стъпки с подмодулите Ще преминем през разработката на прост проект, който ще разделим на основен проект и няколко подпроекта. Нека започнем добавяйки налично Git хранилище като подмодул на това, в което работим. Необходимата ви команда е git submodule add с абсолютния или релативен URL на проекта, който искаме да започнем да следим. В нашия пример ще включим библиотека наречена “DbConnector”. $ git submodule add https://github.com/chaconinc/DbConnector Cloning into 'DbConnector'... remote: Counting objects: 11, done. remote: Compressing objects: 100% (10/10), done. remote: Total 11 (delta 0), reused 11 (delta 0) Unpacking objects: 100% (11/11), done. Checking connectivity... done. По подразбиране, подмодулите се добавят в директории съответстващи на имената на хранилищата им, в този случай “DbConnector”. Ако искате да са в различен път, добавяте го като параметър в края на командата. Ако сега изпълним git status ще видим няколко неща. $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: .gitmodules new file: DbConnector На първо място е новият файл .gitmodules . Това е конфигурационен файл, който съхранява съответствието между URL-а на проекта и локалната директория, в която сме го изтеглили: [submodule "DbConnector"] path = DbConnector url = https://github.com/chaconinc/DbConnector При повече подмодули, ще имате и повече секции в този файл. Важно е да посочим, че този файл попада под контрол на версиите както и другите ви файлове като .gitignore . Това значи, че ще се тегли и публикува с останалата част от проекта. Това се прави, за да може други хора, които клонират проекта да ви да знаят откъде да вземат проектите на подмодулите. Забележка Понеже URL-ите в .gitmodules файла са мястото, от което другите хора първо ще опитат да клонират/теглят, уверете се доколкото е възможно, че това са адреси до които те имат достъп. Например, ако използвате различен URL за публикуване от този който другите ще ползват за теглене, постарайте се да ползвате този, до който другите имат достъп. Можете да коригирате тази стойност локално с git config submodule.DbConnector.url PRIVATE_URL за ваше собствено ползване. Когато е възможно, релативните адреси могат да са полезни. Друга интересна информация от изхода на git status е елемента с директорията на проекта. Ако изпълните git diff ще видите нещо любопитно: $ git diff --cached DbConnector diff --git a/DbConnector b/DbConnector new file mode 160000 index 0000000..c3f01dc --- /dev/null +++ b/DbConnector @@ -0,0 +1 @@ +Subproject commit c3f01dc8862123d317dd46284b05b6892c7b29bc Въпреки че DbConnector е поддиректория в работната ви директория, Git я вижда като подмодул и не следи съдържанието ѝ когато сте извън нея. Вместо това, Git я третира като отделен къмит. Ако искате малко по-приятен diff изход, може да подадете --submodule параметъра към git diff . $ git diff --cached --submodule diff --git a/.gitmodules b/.gitmodules new file mode 100644 index 0000000..71fc376 --- /dev/null +++ b/.gitmodules @@ -0,0 +1,3 @@ +[submodule "DbConnector"] + path = DbConnector + url = https://github.com/chaconinc/DbConnector Submodule DbConnector 0000000...c3f01dc (new submodule) Когато къмитнете, виждате нещо такова: $ git commit -am 'Add DbConnector module' [master fb9093c] Add DbConnector module 2 files changed, 4 insertions(+) create mode 100644 .gitmodules create mode 160000 DbConnector Забележете режима 160000 за елемента DbConnector . Това е специфичен режим в Git, който в общи линии показва, че записвате къмит като директория, вместо като поддиректория или файл. Последно, публикуваме промените: $ git push origin master Клониране на проект с подмодули Тук ще клонираме проект с подмодули в него. Когато клонирате подобно хранилище, по подразбиране получавате директориите на подмодулите им, но без съдържание в тях: $ git clone https://github.com/chaconinc/MainProject Cloning into 'MainProject'... remote: Counting objects: 14, done. remote: Compressing objects: 100% (13/13), done. remote: Total 14 (delta 1), reused 13 (delta 0) Unpacking objects: 100% (14/14), done. Checking connectivity... done. $ cd MainProject $ ls -la total 16 drwxr-xr-x 9 schacon staff 306 Sep 17 15:21 . drwxr-xr-x 7 schacon staff 238 Sep 17 15:21 .. drwxr-xr-x 13 schacon staff 442 Sep 17 15:21 .git -rw-r--r-- 1 schacon staff 92 Sep 17 15:21 .gitmodules drwxr-xr-x 2 schacon staff 68 Sep 17 15:21 DbConnector -rw-r--r-- 1 schacon staff 756 Sep 17 15:21 Makefile drwxr-xr-x 3 schacon staff 102 Sep 17 15:21 includes drwxr-xr-x 4 schacon staff 136 Sep 17 15:21 scripts drwxr-xr-x 4 schacon staff 136 Sep 17 15:21 src $ cd DbConnector/ $ ls $ Директорията DbConnector е тук, но е празна. Трябва да изпълните две команди: git submodule init за да инициализирате вашия локален конфигурационен файл и след това git submodule update за да издърпате данните за подмодулите и да попълните директориите им със съдържанието на последните им къмити: $ git submodule init Submodule 'DbConnector' (https://github.com/chaconinc/DbConnector) registered for path 'DbConnector' $ git submodule update Cloning into 'DbConnector'... remote: Counting objects: 11, done. remote: Compressing objects: 100% (10/10), done. remote: Total 11 (delta 0), reused 11 (delta 0) Unpacking objects: 100% (11/11), done. Checking connectivity... done. Submodule path 'DbConnector': checked out 'c3f01dc8862123d317dd46284b05b6892c7b29bc' Сега DbConnector поддиректорията е в същия статус, в който я къмитнахте по-рано. Има и по-лесен начин да направите това. Ако подадете параметър --recurse-submodules на git clone , целият този процес ще бъде свършен от автоматично - Git ще инициализира и обнови всеки подмодул в хранилището, включително вложените такива, ако съществуват в хранилището. $ git clone --recurse-submodules https://github.com/chaconinc/MainProject Cloning into 'MainProject'... remote: Counting objects: 14, done. remote: Compressing objects: 100% (13/13), done. remote: Total 14 (delta 1), reused 13 (delta 0) Unpacking objects: 100% (14/14), done. Checking connectivity... done. Submodule 'DbConnector' (https://github.com/chaconinc/DbConnector) registered for path 'DbConnector' Cloning into 'DbConnector'... remote: Counting objects: 11, done. remote: Compressing objects: 100% (10/10), done. remote: Total 11 (delta 0), reused 11 (delta 0) Unpacking objects: 100% (11/11), done. Checking connectivity... done. Submodule path 'DbConnector': checked out 'c3f01dc8862123d317dd46284b05b6892c7b29bc' Ако вече сте клонирали проект, но сте забравили --recurse-submodules , може да комбинирате стъпките git submodule init и git submodule update изпълнявайки git submodule update --init . За да инициализирате, изтеглите и извлечете в работната директория всички вложени подмодули, може да използвате и git submodule update --init --recursive . Работа по проект с подмодули Сега имаме копие от проекта с подмодули в него и ще работим заедно с колегите си както по основния проект, така и по подмодула. Издърпване на Upstream промени от Submodule Remote Най-простият модел на работа с подмодули е просто да ги ползвате в проекта си без да ги модифицирате и от време на време да проверявате за промени по тях. Да видим малък пример. Ако искате да проверите за нова работа в даден подмодул, можете да влезете в директорията му и да изпълните git fetch и git merge към upstream клона. $ git fetch From https://github.com/chaconinc/DbConnector c3f01dc..d0354fc master -> origin/master $ git merge origin/master Updating c3f01dc..d0354fc Fast-forward scripts/connect.sh | 1 + src/db.c | 1 + 2 files changed, 2 insertions(+) Ако сега се върнете в основния проект и изпълните git diff --submodule , може да видите че подмодула е обновен и да получите списък на къмитите добавени в него. Ако не искате да пишете --submodule при всяко изпълнение на git diff , може да зададете опцията като подразбираща се с конфигурационната настройка diff.submodule , на която трябва да дадете стойност “log”. $ git config --global diff.submodule log $ git diff Submodule DbConnector c3f01dc..d0354fc: > more efficient db routine > better connection routine Ако къмитнете на този етап, ще заключите подмодула да получава нов код, когато други хора ъпдейтват. Има и по-лесен начин да направите това, ако не ви се иска ръчно да дърпате и сливате в поддиректориите. Ако изпълните git submodule update --remote , Git ще премине през подмодулите, ще ги изтегли и ще ги обнови вместо вас. $ git submodule update --remote DbConnector remote: Counting objects: 4, done. remote: Compressing objects: 100% (2/2), done. remote: Total 4 (delta 2), reused 4 (delta 2) Unpacking objects: 100% (4/4), done. From https://github.com/chaconinc/DbConnector 3f19983..d0354fc master -> origin/master Submodule path 'DbConnector': checked out 'd0354fc054692d3906c85c3af05ddce39a1c0644' Командата по подразбиране приема, че желаете да обновите съдържанието на master клона в хранилището на подмодула (този, към който сочи HEAD в отдалеченото хранилище). Но можете да промените това поведение, ако желаете. Например, ако искате DbConnector подмодула да следи клона “stable” от хранилището си, можете да зададете това или в .gitmodules файла (така че и всички останали да следят този клон) или само в локалния ви файл .git/config . Нека използваме .gitmodules : $ git config -f .gitmodules submodule.DbConnector.branch stable $ git submodule update --remote remote: Counting objects: 4, done. remote: Compressing objects: 100% (2/2), done. remote: Total 4 (delta 2), reused 4 (delta 2) Unpacking objects: 100% (4/4), done. From https://github.com/chaconinc/DbConnector 27cf5d3..c87d55d stable -> origin/stable Submodule path 'DbConnector': checked out 'c87d55d4c6d4b05ee34fbc8cb6f7bf4585ae6687' Ако пропуснете частта -f .gitmodules командата ще направи промяната само за вас, но вероятно е по-смислено да следите тази информация с хранилището, така че всички останали да правят същото. Когато пуснем git status сега, Git ще ни покаже, че имаме “нови къмити” в подмодула. $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: .gitmodules modified: DbConnector (new commits) no changes added to commit (use "git add" and/or "git commit -a") Ако активирате конфигурационната настройка status.submodulesummary , Git също така ще ви показва кратък списък на промените в подмодулите ви: $ git config status.submodulesummary 1 $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: .gitmodules modified: DbConnector (new commits) Submodules changed but not updated: * DbConnector c3f01dc...c87d55d (4): > catch non-null terminated lines Изпълнението на git diff сега ще ни покаже, че сме модифицирали .gitmodules файла ни и че имаме няколко къмита, които сме изтеглили и са готови да бъдат къмитнати в submodule проекта. $ git diff diff --git a/.gitmodules b/.gitmodules index 6fc0b3d..fd1cc29 100644 --- a/.gitmodules +++ b/.gitmodules @@ -1,3 +1,4 @@ [submodule "DbConnector"] path = DbConnector url = https://github.com/chaconinc/DbConnector + branch = stable Submodule DbConnector c3f01dc..c87d55d: > catch non-null terminated lines > more robust error handling > more efficient db routine > better connection routine Това е добре, защото можем в действителност да видим информацията от къмитите, която ще къмитнем в нашия подмодул. Веднъж къмитната, тази информация е видима и по-късно, когато изпълним git log -p . $ git log -p --submodule commit 0a24cfc121a8a3c118e0105ae4ae4c00281cf7ae Author: Scott Chacon <schacon@gmail.com> Date: Wed Sep 17 16:37:02 2014 +0200 updating DbConnector for bug fixes diff --git a/.gitmodules b/.gitmodules index 6fc0b3d..fd1cc29 100644 --- a/.gitmodules +++ b/.gitmodules @@ -1,3 +1,4 @@ [submodule "DbConnector"] path = DbConnector url = https://github.com/chaconinc/DbConnector + branch = stable Submodule DbConnector c3f01dc..c87d55d: > catch non-null terminated lines > more robust error handling > more efficient db routine > better connection routine По подразбиране Git ще се опитва да обновява всички подмодули при изпълнение на git submodule update --remote . Ако те са повечко, можете да подадете само името на този, който желаете да обновите. Издърпване на Upstream промени от Project Remote Нека сега се поставим в ролята на вашия сътрудник, който има собствено локално копие на MainProject хранилището. Само изпълнението на git pull за издърпване на вашите промени не е достатъчно: $ git pull From https://github.com/chaconinc/MainProject fb9093c..0a24cfc master -> origin/master Fetching submodule DbConnector From https://github.com/chaconinc/DbConnector c3f01dc..c87d55d stable -> origin/stable Updating fb9093c..0a24cfc Fast-forward .gitmodules | 2 +- DbConnector | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: DbConnector (new commits) Submodules changed but not updated: * DbConnector c87d55d...c3f01dc (4): < catch non-null terminated lines < more robust error handling < more efficient db routine < better connection routine no changes added to commit (use "git add" and/or "git commit -a") По подразбиране, git pull рекурсивно изтегля промените по подмодулите, както може да се види от изхода на първата команда отгоре. Обаче, тя не обновява подмодулите. Това е видно от изхода на git status , която показва, че подмодулът е “modified”, и че има “new commits”. В допълнение, скобите показващи новите къмити сочат наляво (<), което значи, че тези нови къмити са записани в MainProject, но не са налични в локалното DbConnector работно копие. За да финализирате обновлението, ще трябва да изпълните git submodule update : $ git submodule update --init --recursive Submodule path 'vendor/plugins/demo': checked out '48679c6302815f6c76f1fe30625d795d9e55fc56' $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean Отбележете, че за да сте напълно сигурни, би трябвало да изпълните git submodule update с флага --init (в случай че MainProject къмитите, които току що сте издърпали, добавят нови подмодули), и с --recursive флага, ако някой от подмодулите съдържат вложени подмодули. Ако искате да автоматизирате този процес, може да добавите флага --recurse-submodules към git pull (от версия на Git 2.14). Това ще накара Git д аизпълни git submodule update веднага след изтеглянето, което да постави подмодулите в коректен режим. Освен това, ако желаете Git винаги да тегли с --recurse-submodules , може да укажете това с конфигурационната опция submodule.recurse (това ще важи от версия 2.15 и нагоре). Така Git ще използва флага --recurse-submodules за всички команди, които го поддържат (с изключение на clone ). Съществува специална ситуация, която може да възникне при издърпване на промени от подпроект: може upstream хранилището да е променило адреса на подмодула в .gitmodules файла в някой от къмитите, които теглите. Това може да стане, ако например проектът на подмодула е със сменена хостинг платформа. В такъв случай е възможно командите git pull --recurse-submodules , или git submodule update да не успеят, ако главният проект сочи към къмит на подмодул, който не се намира в локално конфигурирания в хранилището submodule remote. За да се избегне тази ситуация е необходима командата git submodule sync : # copy the new URL to your local config $ git submodule sync --recursive # update the submodule from the new URL $ git submodule update --init --recursive Работа по подмодул Ако ползвате подмодули, твърде вероятно е да искате да работите и по техния код едновременно с основния проект. В противен случай може да предпочетете да ползвате по-проста dependency management система като Maven или Rubygems. Да разгледаме пример с промяна на кода на подмодул и на основния проект, къмитване и публикуване на промените. Досега, когато изпълнявахме git submodule update командата за да изтеглим промените от хранилищата на подмодулите, Git ще взема новия код и ще обновява файловете в поддиректориите, но ще ги остави в режим известен като “detached HEAD”. Това означава, че нямаме работещ локален клон (като master например) следящ промените. Липсата на такъв клон означава, че дори да къмитнете промени по подмодула, тези промени е твърде вероятно да се загубят при следващото изпълнение на git submodule update . Необходими са малко допълнителни стъпки, ако искате промените в подмодул да бъдат следени. Две неща трябва да се направят. Трябва да отидете в директорията на всеки подмодул и да стартирате клон, по който да работите. След това трябва да инструктирате Git как да действа, ако сте направили промени и след това git submodule update --remote внесе нови данни от upstream хранилището. Опциите са да можете да ги слеете с локалната ви работа или да се опитате да пребазирате локалната работа върху новите промени. Първо, да влезем в директория на подмодул и да създадем клон. $ cd DbConnector/ $ git checkout stable Switched to branch 'stable' Нека опитаме с опцията “merge”. За да я подадем ръчно, добавяме --merge към update повикването. Тук ще видим, че на сървъра е имало промяна в кода на този подмодул и тя се слива. $ cd .. $ git submodule update --remote --merge remote: Counting objects: 4, done. remote: Compressing objects: 100% (2/2), done. remote: Total 4 (delta 2), reused 4 (delta 2) Unpacking objects: 100% (4/4), done. From https://github.com/chaconinc/DbConnector c87d55d..92c7337 stable -> origin/stable Updating c87d55d..92c7337 Fast-forward src/main.c | 1 + 1 file changed, 1 insertion(+) Submodule path 'DbConnector': merged in '92c7337b30ef9e0893e758dac2459d07362ab5ea' Ако влезем в DbConnector директорията, ще имаме новите данни слети в локалния stable клон. Сега нека видим какво се случва, ако направим наша собствена промяна в библиотеката и някой друг публикува друга upstream промяна по същото време. $ cd DbConnector/ $ vim src/db.c $ git commit -am 'Unicode support' [stable f906e16] Unicode support 1 file changed, 1 insertion(+) Пускаме обновяването на подмодула при едновременно налични локална и отдалечена промяна, която трябва да внедрим. $ cd .. $ git submodule update --remote --rebase First, rewinding head to replay your work on top of it... Applying: Unicode support Submodule path 'DbConnector': rebased into '5d60ef9bbebf5a0c1c1050f242ceeb54ad58da94' Ако забравите --rebase или --merge , Git просто ще обнови подмодула до съдържанието на сървъра и ще върне проекта в режим detached HEAD. $ git submodule update --remote Submodule path 'DbConnector': checked out '5d60ef9bbebf5a0c1c1050f242ceeb54ad58da94' Ако това се случи, не е голям проблем, можете просто да се върнете в директорията и да извлечете клона отново (той все още ще съдържа вашата работа), след което да слеете или пребазирате origin/stable (или който и да е отдалечен клон) ръчно. Ако не сте къмитнали промените си в подмодула и пуснете обновяване, което би могло да предизвика проблеми, Git ще издърпа промените, но няма да презапише несъхранената работа в поддиректорията. $ git submodule update --remote remote: Counting objects: 4, done. remote: Compressing objects: 100% (3/3), done. remote: Total 4 (delta 0), reused 4 (delta 0) Unpacking objects: 100% (4/4), done. From https://github.com/chaconinc/DbConnector 5d60ef9..c75e92a stable -> origin/stable error: Your local changes to the following files would be overwritten by checkout: scripts/setup.sh Please, commit your changes or stash them before you can switch branches. Aborting Unable to checkout 'c75e92a2b3855c9e5b66f915308390d9db204aca' in submodule path 'DbConnector' Също, ако сте направили промени, които водят до конфликт с нещо променено в upstream-а, Git ще ви уведоми за това. $ git submodule update --remote --merge Auto-merging scripts/setup.sh CONFLICT (content): Merge conflict in scripts/setup.sh Recorded preimage for 'scripts/setup.sh' Automatic merge failed; fix conflicts and then commit the result. Unable to merge 'c75e92a2b3855c9e5b66f915308390d9db204aca' in submodule path 'DbConnector' Можете да влезете в поддиректорията и да оправите конфликта по нормалния начин. Публикуване на промени по подмодул Сега имаме промени в директорията на подмодула. Някои от тях идват от upstream-а след обновяване а други са направени ръчно локално и не са достъпни за никой друг, защото все още не сме ги публикували. $ git diff Submodule DbConnector c87d55d..82d2ad3: > Merge from origin/stable > Update setup script > Unicode support > Remove unnecessary method > Add new option for conn pooling Ако къмитваме в главния проект и го публикуваме без да включим промените в подмодула, то другите хора, които ползват кода ни ще бъдат в затруднение, защото няма да имат начин да се се сдобият с тези промени, а коректната работа на основния проект може да зависи от тях. Тези промени ще са само в локалното ви копие. За да сте сигурни, че това няма да се случва, можете да укажете на Git да проверява дали всички подмодули са публикувани успешно преди да публикува основния проект. Командата git push приема аргумента --recurse-submodules , който може да се зададе със стойности “check” или “on-demand”. Стойността “check” ще направи така, че публикуването да бъде отказано, ако произволна къмитната промяна в подмодул не е била публикувана успешно. $ git push --recurse-submodules=check The following submodule paths contain changes that can not be found on any remote: DbConnector Please try git push --recurse-submodules=on-demand or cd to the path and use git push to push them to a remote. Както се вижда, получавате и напътствия как бихте могли да продължите. Най-простата възможност е да преминете през директориите на всички подмодули и ръчно да публикувате съдържанието им, след което да се върнете и да пробвате да публикувате главния проект. Ако искате това поведение с проверка да е валидно за всички публикувания, можете да изпълните git config push.recurseSubmodules check Другата опция е да използвате стойността “on-demand”, което ще опита да свърши работата за вас. $ git push --recurse-submodules=on-demand Pushing submodule 'DbConnector' Counting objects: 9, done. Delta compression using up to 8 threads. Compressing objects: 100% (8/8), done. Writing objects: 100% (9/9), 917 bytes | 0 bytes/s, done. Total 9 (delta 3), reused 0 (delta 0) To https://github.com/chaconinc/DbConnector c75e92a..82d2ad3 stable -> stable Counting objects: 2, done. Delta compression using up to 8 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (2/2), 266 bytes | 0 bytes/s, done. Total 2 (delta 1), reused 0 (delta 0) To https://github.com/chaconinc/MainProject 3d6d338..9a377d1 master -> master Както се вижда тук, Git е отишъл в DbConnector модула и е публикувал него преди да опита Push за главния проект. Ако по някаква причина този подмодул не успее да се публикува, главния проект също няма да успее. За да направите това поведение подразбиращо се, изпълнете git config push.recurseSubmodules on-demand . Сливане на промени в подмодул Ако промените референция на подмодул по същото време като някой друг, може да възникнат проблеми. Това е ситуация, при която историите на подмодул са се разделили и са къмитнати в разделящи се клонове в суперпроект. Ако единият от къмитите е директен предшественик на другия (fast-forward merge), тогава Git просто ще избере последния за сливането, така че това работи добре. Обаче, Git няма да опита да направи за вас дори и тривиално сливане. Ако къмитите на подмодул се разделят и трябва да се слеят, ще получите нещо такова: $ git pull remote: Counting objects: 2, done. remote: Compressing objects: 100% (1/1), done. remote: Total 2 (delta 1), reused 2 (delta 1) Unpacking objects: 100% (2/2), done. From https://github.com/chaconinc/MainProject 9a377d1..eb974f8 master -> origin/master Fetching submodule DbConnector warning: Failed to merge submodule DbConnector (merge following commits not found) Auto-merging DbConnector CONFLICT (submodule): Merge conflict in DbConnector Automatic merge failed; fix conflicts and then commit the result. Какво се случва тук? Git е установил, че двата клона пазят точки от историята на подмодула, които са разделени и трябва да се слеят. Това установяваме от съобщението “merge following commits not found”, което само по себе си е объркващо, но ще обясним какво иска да каже след малко. За да решите проблема, трябва да установите в какъв статус би трябвало да е модула. Странно, но Git тук в действителност не ви помага с информация, не посочва дори SHA-1 хеш стойностите на къмитите от двете страни на историята. За щастие, това е лесно за извличане. Ако пуснете git diff можете да получите SHA-1 стойностите на къмитите в двата клона, които сте се опитали да слеете. $ git diff diff --cc DbConnector index eb41d76,c771610..0000000 --- a/DbConnector +++ b/DbConnector В този случай, eb41d76 е къмитът в нашия подмодул, който ние сме имали и c771610 е upstream къмита. Ако отидем в поддиректорията на модула, той вече трябва да е на eb41d76 , защото сливането не го е променило. Ако по някаква причина не е, може просто да създадете нов клон сочещ към него. Важната част е SHA-1 стойността на къмита от другата страна. Това е, което трябва да слеете и коригирате. Можете или да опитате сливане с SHA-1 стойността директно или може да създадете клон за нея и да опитате сливането в него. Бихме препоръчали второто, дори само за да създадете по-добро merge commit съобщение. И така, ще отидем в поддиректорията, ще създадем клон наречен “try-merge”, базиран на тази втора SHA-1 стойност, изведена от git diff и ще слеем ръчно. $ cd DbConnector $ git rev-parse HEAD eb41d764bccf88be77aced643c13a7fa86714135 $ git branch try-merge c771610 $ git merge try-merge Auto-merging src/main.c CONFLICT (content): Merge conflict in src/main.c Recorded preimage for 'src/main.c' Automatic merge failed; fix conflicts and then commit the result. Тук получихме конфликт, така че ако го разрешим и къмитнем, тогава просто можем да обновим главния проект с резултата. $ vim src/main.c (1) $ git add src/main.c $ git commit -am 'merged our changes' Recorded resolution for 'src/main.c'. [master 9fd905e] merged our changes $ cd .. (2) $ git diff (3) diff --cc DbConnector index eb41d76,c771610..0000000 --- a/DbConnector +++ b/DbConnector @@@ -1,1 -1,1 +1,1 @@@ - Subproject commit eb41d764bccf88be77aced643c13a7fa86714135 -Subproject commit c77161012afbbe1f58b5053316ead08f4b7e6d1d ++Subproject commit 9fd905e5d7f45a0d4cbc43d1ee550f16a30e825a $ git add DbConnector (4) $ git commit -m "Merge Tom's Changes" (5) [master 10d2c60] Merge Tom's Changes Първо разрешаваме конфликта. Връщаме се в директорията на основния проект. Можем да проверим SHA-1 стойностите отново. Разрешаваме конфликтния submodule обект. Къмитваме сливането ни. Може да е леко смущаващо, но не е толкова трудно. Съществува и още един интересен случай, който Git обработва. Ако в директорията на подмодула съществува merge къмит, който съдържа и двата къмита в историята си, Git ще ви го предложи като възможно решение. Той вижда, че на даден етап от този submodule проект, някой вече е слял клоновете съдържащи тези два къмита, така че може да искате този къмит. Ето защо объркващото съобщение от по-горе гласеше “merge following commits not found”, защото системата не може да направи това . Объркващият текст идва, защото едвали някой би очаквал Git дори да опита да направи това. Ако вместо това Git намери приемлив сливащ къмит, ще видите нещо от рода: $ git merge origin/master warning: Failed to merge submodule DbConnector (not fast-forward) Found a possible merge resolution for the submodule: 9fd905e5d7f45a0d4cbc43d1ee550f16a30e825a: > merged our changes If this is correct simply add it to the index for example by using: git update-index --cacheinfo 160000 9fd905e5d7f45a0d4cbc43d1ee550f16a30e825a "DbConnector" which will accept this suggestion. Auto-merging DbConnector CONFLICT (submodule): Merge conflict in DbConnector Automatic merge failed; fix conflicts and then commit the result. Това, което ви се предлага е да обновите индекса както ако бяхте изпълнили git add (което изчиства конфликта) и след това да къмитнете. Но вероятно не трябва да правите това. Можете също толкова лесно да влезете в поддиректорията, да видите каква е разликата, да направите fast-forward до този къмит, да го тествате и след това да къмитнете. $ cd DbConnector/ $ git merge 9fd905e Updating eb41d76..9fd905e Fast-forward $ cd .. $ git add DbConnector $ git commit -am 'Fast forward to a common submodule child' Това ви дава същия резултат, но най-малкото по този начин може да проверите, че нещата работят и разполагате с кода в поддиректорията когато сте готови. Съвети Можете да улесните работата си с подмодули по няколко начина. Foreach команда Съществува foreach команда, която ви позволява да изпълнявате други команди за всеки подмодул, като в цикъл. Това е полезно, ако имате много подмодули в проекта. Да кажем, че стартираме работа по нова функционалност или оправяме грешка и същевременно имаме текущо свършена работа в няколко подмодула. Можем лесно да маскираме (stash) работата по всички подмодули наведнъж. $ git submodule foreach 'git stash' Entering 'CryptoLibrary' No local changes to save Entering 'DbConnector' Saved working directory and index state WIP on stable: 82d2ad3 Merge from origin/stable HEAD is now at 82d2ad3 Merge from origin/stable След това, можем да създадем и превключим към нов клон във всички подмодули едновременно. $ git submodule foreach 'git checkout -b featureA' Entering 'CryptoLibrary' Switched to a new branch 'featureA' Entering 'DbConnector' Switched to a new branch 'featureA' В общи линии получавате представа. Едно наистина полезно нещо е, че можете да изведете добре изглеждащ унифициран diff на това какво се е променило в главния проект и също във всички подмодули. $ git diff; git submodule foreach 'git diff' Submodule DbConnector contains modified content diff --git a/src/main.c b/src/main.c index 210f1ae..1f0acdc 100644 --- a/src/main.c +++ b/src/main.c @@ -245,6 +245,8 @@ static int handle_alias(int *argcp, const char ***argv) commit_pager_choice(); + url = url_decode(url_orig); + /* build alias_argv */ alias_argv = xmalloc(sizeof(*alias_argv) * (argc + 1)); alias_argv[0] = alias | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/software/loom/use-case/support | 将视频信息用于客户支持服务 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费试用 功能 探索功能 会议记录 录屏工具 截图 Loom AI 正在编辑 Back 解决方案 Teams 用例 公司规模 Teams 销售 营销 设计 支持 产品管理 工程 用例 Loom + Jira Loom + Confluence 公司规模 Enterprise Back 资源 定价 更多 + 更少 - 免费试用 Back 免费试用 适用于支持团队的 Loom 利用视频信息提升客户服务 Loom 通过大规模个性化客户互动，帮助团队将客户转化为终身粉丝 免费获取 Loom 利用视频建立客户融洽关系 客户可以观看视频，而不是阅读冗长的电子邮件。创建高质量的客户服务内容，教育买家并提高客户参与度。 视频很及时 以个性化的方式解决客户关注的问题，从而更快地完成反馈循环。 视频是个性化的 创建定制视频，以清晰的视觉效果帮助客户最大限度地了解您的产品。 视频是互动的 跟踪视频互动情况，发现客户何时需要额外支持。 客户支持功能 轻松录制 通过浏览器、台式机或手机捕捉屏幕，满足客户需求。 随时随地共享 通过电子邮件、聊天、网络或社交媒体发送 Loom，无需下载即可观看。 集成工具 Loom 可与 Zendesk 等客户服务工具配合使用，以简化支持。 查看观看情况 了解客户何时以及如何与您的客户支持视频互动。 品牌支持 添加公司徽标和调色板，打造统一的品牌形象。 继续提供帮助 直接在视频中查看评论并提供其他支持服务。 帮助用户并提高客户满意度 通过高质量的客户服务视频为用户提供支持。 个性化风格可提高用户留存率 拥有个性化品牌体验的客户更有可能成为回头客。Loom 可以轻松实现个性化，从而提高客户的终身价值。 视频支持是高质量的支持 视频是与客户互动的一种更生动的方式，也更有价值。例如，如果客户能看到产品功能的工作方式，就更容易学会使用该功能。 个性化可避免客户流失 超过 60% 的客户会因为品牌提供的非个性化体验而流失。Loom 增加了减少客户流失和提高客户满意度指标所需的个性化风格。 “Loom，那个在角落带有小脸气泡的功能太强大了。它的效果要比在动画或幻灯片上运行音频轨道的传统形式好得多。在角落放上一张真实的面孔增添了个人特色，使故事讲述更加生动。” Pearson 客户成功部 Erica Goodell Loom AI 为服务客户的人提供服务 明确的信息 Loom AI 会自动去除填充词并删除停顿。 最后的润色 使用 Loom AI 生成标题、摘要和章节，以提高参与度和清晰度。 即时共享 Loom AI 可在瞬间起草电子邮件，以获得精美的演示文稿。 免费试用 Loom AI 更快录制，有更多时间专注于客户 通过快速、精确的编辑和简便的剪辑管理，告别重复录制。现在，通过异步视频提供卓越的客户服务易如反掌。 试试看 来自我们的博客 如何使用异步视频改善客户支持 客户支持流程需要视频的 4 个理由 阅读文章 我们如何在客户支持策略中利用视频 阅读文章 浏览我们的博客 探索使用 Loom 的方法 适用于工程团队的 Loom 了解更多 适用于销售团队的 Loom 了解更多 适用于项目管理团队的 Loom 了解更多 查看所有用例 无论您身在何处，Loom 都能工作 适用于 Mac、Windows、iOS 和 Android 免费获取 Loom 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://www.digitalcameraworld.com/buying-guides/the-best-150-600mm-lenses#section-faqs | The best 150-600mm lenses | Digital Camera World Skip to main content Open menu Close main menu Digital Camera World THE HOME OF DIGITAL PHOTOGRAPHY US Edition US Canada UK Australia Subscribe Sign in View Profile Sign out Search Search Digital Camera World Cameras Accessories Tech How To Reviews Buying Guides Magazines Bokeh Face Podcast The Photography & Video Show Digital Camera Australian Camera Australian ProPhoto About Us Photography Magazines Why subscribe? Issues filled with product reviews, latest updates, expert advice and more Delivered to your Android or IOS device Every issue is packed with photo tips, kit reviews and inspiration From $12 Subscribe now Jump to: The quick list 150-600mm lenses Sigma 150-600mm Sports Tamron 150-600mm G2 OM System 150-600mm 150-600mm alternatives Nikon Z 180-600mm Canon RF 100-500mm Sony 200-600mm Tamron 150-500mm Sigma 60-600mm Fuji XF150-600mm Comparisons How to choose How we test lenses FAQS Don't miss these Lenses If I were starting my Pro Sports Photography career again, I’d buy this 180-600mm lens - it's currently got $200 off and under $2,000 Compact Cameras The best full-frame compact cameras – portable powerhouses DSLR Cameras The best DSLR in 2025: Chunky, classic camera designs still loved today Lenses The best lenses for the Canon EOS R50: this camera is a proper little powerhouse and deserves the right lenses Bridge Cameras The best bridge camera: ultra-zoom cameras for far-off subjects Lenses 12 lenses of Christmas: Laowa and Viltrox try to outdo each other for most new lenses in the same month! Lenses The best Nikon Z lenses: the top buys for your Nikon Z-series mirrorless Cameras The best Panasonic Lumix cameras: from Micro Four Thirds to full-frame and bridge cameras Lenses Hands-on Canon RF 45mm f/1.2 STM review: The super-fast glass that's super affordable – and punches way above its price point Lenses The best lenses for the Sony ZV-E10 & ZV-E10 II: smart choices for vlogging and just about any other genre of video and stills photography Lenses The best lenses for the Canon EOS M50 and M50 Mark II: these mini marvels will make the most of your slimline camera Lenses The best Nikon lenses for DSLRs in 2026: brilliant lenses for Nikon F-mount cameras Lenses The best lenses for the Sony A6400: let me help you pick some perfect lenses for your pocket powerhouse Sony body Cameras Best camera for macro photography in 2025: This gear gets great close-up shots! Lenses The best lenses for the Fujifilm X-T5: make the most of all those megapixels Popular Camera news Camera rumors Photo mag deals Photography & Video Show Cheatsheets Cameras Lenses The best 150-600mm lenses: super-telephoto zooms to get close to the action Buying guides By Matthew Richards Contributions from Lauren Scott last updated 22 December 2025 These are the best 150-600mm lenses to really cover the distance for action, sports and wildlife photography When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works . (Image credit: Lauren Scott) Jump to: The quick list 150-600mm lenses Sigma 150-600mm Sports Tamron 150-600mm G2 OM System 150-600mm 150-600mm alternatives Nikon Z 180-600mm Canon RF 100-500mm Sony 200-600mm Tamron 150-500mm Sigma 60-600mm Fuji XF150-600mm Comparisons How to choose How we test lenses FAQS Share Share by: Copy link Facebook X Whatsapp Pinterest Flipboard Share this article Join the conversation Follow us Add us as a preferred source on Google I don’t like to think I’m lazy and I honestly don’t mind ‘zooming with my feet’, but that’s not always possible. To get as close as I’d ideally like, I’d have to jump the barriers at sporting events, sprout my own pair of wings at airshows, and risk getting eaten alive by hungry wildlife. Sometimes discretion is the better part of valor, and a 150-600mm lens can get you close to the action from a respectable (and safe) distance. Originally pioneered by Sigma and adopted by Tamron , 150-600mm lenses used to be a rare breed. Camera manufacturers often didn’t make their own and even if they did, some of the old DSLR examples have now been discontinued. To make this guide as useful as possible, I've included not only ‘150-600mm’ lenses that are currently available, but also a selection of super-telephoto zooms that cover a fairly similar range. The debate on the 'best' zoom range, of course, rages on – many photographers prefer the best 70-200mm lenses or the best 100-400mm lenses as their favorite working distance. However, the 150-600mm outstrips them both in terms of sheer range and raw distance. Matthew Richards Social Links Navigation Lens tester Matthew Richards is a photographer and journalist who has spent years using and reviewing all manner of photo gear. He is Digital Camera World's principal lens reviewer, and as such he has tested more primes and zooms – including plenty of 150-600mm optics – than most people have had hot dinners! The quick list Best mirrorless 1. Sigma 150-600mm f/5-6.3 DG DN OS Sports View at Amazon View at Adorama View at Adorama View at Best Buy Best for mirrorless For Sony E and L-mount mirrorless cameras, this lens is a worthy successor to a DSLR classic. It's got a weather-sealed build and produces pin-sharp imagery. Read more below Best DSLR 2. Tamron SP 150-600mm f/5-6.3 Di VC USD G2 View at Amazon Best for DSLRs Still going strong for Nikon F and Canon EF mounts, Tamron's G2 lens is a refresh of a classic that boasts excellent autofocus and stabilisation. Read more below Best MFT 3. Olympus M.Zuiko 75-300mm f/4.8-6.7 II View at Amazon View at Adorama View at Best Buy Preorder at BHPhoto Best Micro Four Thirds Delivering a 300-1200mm equivalent zoom range thanks to the MFT crop factor, this is an incredibly powerful super-tele zoom that doubles your reach. Read more below Best Nikon Z 4. Nikon Z 180-600mm f/5.6-6.3 VR View at BHPhoto View at Adorama View at Amazon View at Best Buy Best Nikon Z Running very close to the 150-600mm focal range, this lens shaves a bit off the wide end, but still delivers real shooting versatility in a lightweight package. Read more below Best Canon RF 5. Canon RF 100-500mm f/4.5-7.1L IS USM View at Amazon View at Adorama View at Crutchfield View at Target Best Canon RF You lose a little at the tele end but gain a little at the wide end, and Canon's RF 100-500mm delivers brilliant images throughout the whole range. Read more below Best Sony 6. Sony FE 200-600mm F5.6-6.3 G OSS View at Adorama View at Best Buy View at Amazon View at Target Best Sony While Sony users can use Sigma's true 150-600mm, this capable telezoom is a solid Sony-made alternative. The optical stabilisation is highly effective. Read more below Load the next products ↴ Multi-mount mirrorless 7. Tamron 150-500mm f/5-6.7 Di III VC VXD View at KEH Camera View at Adorama View at Amazon View at Best Buy Multi-mount mirrorless Originally just for Sony FE mount, this zoom lens from Tamron has since been made available for Fujifilm X and Nikon Z. It's not quite 600mm, but it's still a great lens. Read more below 10x zoom 8. Sigma 60-600mm f/5-6.3 DG OS HSM | S View at Amazon View at Amazon 10x zoom Need a little more play at the wide end? This Sigma-made lens offers a whopping 10x zoom range for DSLR shooters, and optically it impresses. Read more below Best Fuji 9. Fujifilm XF150-600mm F5.6-8 R LM OIS WR View at Adorama View at Amazon View at Best Buy View at Target Best Fujifilm X Delivering a whopping equivalent zoom range of 229-914mm, this lens certainly provides telephoto reach. It can even be used with 1.4x and 2.0x teleconverters! Read more below Best 150-600mm lenses Why you can trust Digital Camera World Our expert reviewers spend hours testing and comparing products and services so you can choose the best for you. Find out how we test. 150-600mm lenses Here are my picks of the best 150-600mm lenses you can buy right now, for both mirrorless and DSLR cameras. Sigma 150-600mm Sports (Image credit: Digital Camera World) 1. Sigma 150-600mm f/5-6.3 DG DN OS Sports The Sports lens finally comes to E-mount and L-mount mirrorless cameras! Our expert review: Specifications Mount: Sony E, Leica L Elements/groups: 25/15 Diaphragm blades: 9 Autofocus: Stepper motor Stabilizer: 4-stops Minimum focus distance: 0.58-2.8m Maximum magnification: 0.34x Filter thread: 95mm Dimensions: 109.4 x 265.6mm Weight: 2,100g Today's Best Deals View at Amazon View at Adorama View at Adorama View at Best Buy Reasons to buy + Superb sharpness + One of few mirrorless options Reasons to avoid - Chunky and heavy - Non-removable tripod collar A retooling of an already excellent DSLR lens, the Sigma 150-600mm f/5-6.3 DG DN OS Sports is the complete package for Sony and Leica L shooters. Pairing superb internal optics with an all-around excellent, weather-sealed build, this heavy-duty zoom lens is a big customer, but is really the only game in town for 150-600mm as far as users of the aforementioned mounts are concerned. Of course, that wouldn't matter if the lens itself was no good. Fortunately, it's excellent. The optical path is a little different from the DSLR version, including 25 elements arranged in 15 groups, and it produces impressive sharpness throughout the entirety of the zoom range. There's some inevitable fall-off in the corners, but not enough to worry about, and it's the sort of thing that will be hidden anyway when you're shooting with a shallow depth of field. The autofocus is excellent, though you'll need to make sure your camera is set up in the optimal way to take advantage of it. The build quality of the lens is also impressive – while no one is going to pretend this is a lightweight lens, it handles well, with tactile zoom and focus rings and a series of on-body controls for functions like AF speed, stabilization intensity, and in a new addition for the mirrorless version, Zoom Torque control to adjust the resistance of the zoom ring. This is an all-around excellent lens that's absolutely worth the money for E-mount and L-mount users. See our full Sigma 150-600mm f/5-6.3 DG DN OS Sports review Image 1 of 4 (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) (Image credit: Chris George/Digital Camera World) Swipe to scroll horizontally Features ★★★★★ The lens inherits the high-end features and handling of the older version for DSLRs, in a smaller, lighter package. Design ★★★★★ The design is very refined, while build quality is excellent and includes extensive weather-seals. Performance ★★★★★ Excellent inherent sharpness is further boosted in real terms by highly effective optical stabilization. Value ★★★★★ It’s a pro-grade super-telephoto zoom with a ‘consumer’ price tag, making it standout value. Tamron 150-600mm G2 (Image credit: Future) 2. Tamron SP 150-600mm f/5-6.3 Di VC USD G2 Tamron’s ‘Generation 2’ edition of its 150-600mm lens is seriously revamped Our expert review: Average Amazon review: ☆ ☆ ☆ ☆ ☆ Specifications Mount: Canon EF, Nikon FX, Sony A Elements/groups: 21/13 Diaphragm blades: 9 Autofocus: Ultrasonic (ring-type) Stabilizer: 4.5-stops Minimum focus distance: 2.2m Maximum magnification: 0.16x Filter thread: 95mm Dimensions: 108 x 260mm Weight: 2,010g Today's Best Deals View at Amazon Reasons to buy + Improved autofocus and stabilisation + Good sharpness in long section Reasons to avoid - No optical stabilization in Sony-fit - Sharpness lacking at shorter zoom This G2 (Generation 2) edition of Tamron’s 150-600mm lens is upgraded in pretty much every facet of its features, handling and performance. The LD (Low Dispersion) element count goes from one to three, and BBAR (Broad-Band Anti-Reflection) coatings add to the older lens’s eBAND (Extended Bandwidth and Angular-Dependency) coatings, to further suppress internal reflections. The uprated autofocus system delivers faster performance, better able to track moving subjects and the redesigned VC (Vibration Compensation) system gives class-leading 4.5-stop effectiveness, plus two additional switchable modes. The second mode is for panning and the third applies stabilisation only during exposures, making it easier to track erratically moving objects. However, the optical stabilizer is only featured in the Canon and Nikon mount editions of the lens. With the Sony A-fit edition, you’ll need to rely on in-camera stabilization (note that for Sony mirrorless cameras using the Sony E-mount, you should check out the Tamron 150-500mm f/5-6.7 Di III VC VXD ). Going one better than the Sigma 150-600mm lenses, a new flex zoom lock enables you to lock the zoom at any position, rather than just at settings for which a focal length is marked on the barrel. It also matches the Sigma lenses with compatibility for an optional USB dock, which Tamron calls a ‘TAP-in Console’, for applying customization and firmware upgrades. There’s only a marginal Increase in size and weight over the original Tamron (see below), but the G2 gets superior weather-seals and a fluorine coating on the front element. Overall build quality feels superior. Living up to Tamron’s claims, the G2’s autofocus speed and the effectiveness of its image stabilization are excellent. Image quality is very good overall, but sharpness is a bit of a mixed bag. In our tests, it proved slightly less sharp than the original Tamron lens at short to medium zoom settings, but rather sharper in the 400-600mm sector. It’s a good trade-off, as you’ll usually find yourself using the lens towards the long end of its zoom range. See our full Tamron SP 150-600mm f/5-6.3 Di VC USD G2 review Swipe to scroll horizontally Features ★★★★☆ The ‘Generation 2’ edition of this lens has a strong feature set with upgraded autofocus and stabilization systems. Design ★★★★☆ The design is pretty crafty and I like that this lens is the best part of a kilogram lighter than Sigma’s competing Sports lens for DSLRs. Performance ★★★★☆ Image quality and overall performance are impressive overall but the lens could be sharper at the short end of its zoom range. Value ★★★★☆ The Tamron is keenly priced for a DSLR-focused 150-600mm with high-end specs and handling. OM System 150-600mm (Image credit: James Artaius) 3. OM System M.Zuiko 150-600mm f/5.0-6.3 IS A 150-600mm lens by name, but goes way beyond that in reality Our expert review: Specifications Mount: Micro Four Thirds Elements/groups: 25/15 Diaphragm blades: 9 Autofocus: Yes Stabilizer: Yes (6 stops at 150mm, 5 at 600mm / 7 stops at 150mm, 6 at 600mm with Sync-IS) Minimum focus distance: 0.56-2.8m Maximum magnification: 0.35x (0.7x full frame equivalent) Filter thread: 95mm Dimensions: 264.4x109.4mm (fully extended) Weight: 2,065g Today's Best Deals View at Amazon View at Adorama View at Best Buy Preorder at BHPhoto Reasons to buy + Phenomenal 600-1200mm range + Up to 7 stops of stabilization + IPX1 weather proofing Reasons to avoid - Sharpness is disappointing - A very big and heavy lens - Very expensive The Micro Four Thirds system has a 2x crop factor, relative to a full-frame camera. This means that, although this lens has an advertised 150-600mm focal range, when fitted to an MFT body its field of view will be equivalent to a 300-1200mm full-frame lens. Consequently, this lens offers immense reach for capturing distant subjects, while up to 7 stops of image stabilization helps keep things steady when you're zoomed in to the max. Keen lens nerds may have spotted that this lens looks very similar to the Sigma 150-600mm f/5-6.3 DG DN OS Sports (number 1 on this list). And that's because it is essentially the same lens, adapted for use on Micro Four Thirds bodies. While that has its benefits, as a full-frame lens it does mean the OM System M.Zuiko 150-600mm feels very bulky and heavy compared to more typical MFT optics. During our time reviewing the OM System M.Zuiko 150-600mm , we came away a little disappointed by the lens's overall sharpness, which was significantly down on the performance of the Sigma 150-600mm. But if you must have telescope-rivalling levels of zoom for your Micro Four Thirds camera, this is the only lens to go for. Read our full OM System M.Zuiko 150-600mm f/5.0-6.3 IS review Image 1 of 3 (Image credit: Paul Burrows) (Image credit: Paul Burrows) (Image credit: Paul Burrows) Swipe to scroll horizontally Features ★★★★☆ Top of the features list is the humungous 1200mm maximum ‘effective’ focal length, backed up by as much as 7-stop stabilization. Design ★★★★☆ Build quality is tough, with IPX1 weather-proofing, although it’s big and heavy for a Micro Four Thirds lens. Performance ★★★☆☆ Levels of sharpness are a bit disappointing, especially at longer zoom settings. Value ★★★☆☆ It’s not particularly good value, especially in comparison to the likes of Sigma and Tamron 150-600mm full-frame zooms. 150-600mm alternatives There are a few lenses that give a similar, but slightly different, focal length range to a 150-600mm – and below are some of those which are worth considering: Nikon Z 180-600mm (Image credit: Matthew Richards) 4. Nikon Z 180-600mm f/5.6-6.3 VR A relatively affordable telephoto option for Z-mount mirrorless. Our expert review: Specifications Mount: Nikon Z Elements/groups: 25/17 Diaphragm blades: 9 Autofocus: Linear stepping motor Stabilizer: Yes Min focus distance: 1.3-2.4m Max magnification: 0.25x Filter thread: 95mm Dimensions (WxL): 110x315.5mm Weight: 1955g Today's Best Deals View at BHPhoto View at Adorama View at Amazon View at Best Buy Reasons to buy + Effective 5.5-stop VR + Razor-sharp throughout range + Customisable function buttons Reasons to avoid - Somewhat bulky/heavy - No VR on/off switch This big zoom is as close as Nikon has got to matching the 150-600mm focal length – and it's an outstanding lens. Earning the full five stars in our review, the Nikon Z 180-600mm f/5.6-6.3 VR offers tack-sharp image quality right the way through that zoom range. While it's a relatively hefty lens, it's light enough that you'll be able to use it handheld for a decent chunk of time. We particularly love the four customisable function buttons, which sit just under where the thumb naturally falls. A particular asset of this lens is its optical VR (Vibration Reduction) system, which is rated to provide up to 5.5 stops of effective compensation. This makes the far end of the telephoto much more useable hand-held, and helps you make the most of all that gorgeous sharpness. Great for sports, wildlife and other types of telephoto shooting, the Nikon Z 180-600mm f/5.6-6.3 VR is the best choice for approximating the 150-600mm focal range on Nikon Z cameras. Read our full Nikon Z 180-600mm f/5.6-6.3 VR review Image 1 of 4 (Image credit: Matthew Richards) (Image credit: Matthew Richards) (Image credit: Matthew Richards) (Image credit: Matthew Richards) Swipe to scroll horizontally Features ★★★★★ Compared with Nikon’s F-mount 200-500mm zoom, this one has longer telephoto reach and more effective 5.5-stop optical stabilization. Design ★★★★★ The lens is impeccably built with extensive weather-seals and is noticeably lighter than Nikon’s 200-500mm lens. Performance ★★★★★ Sharpness and clarity are exceptional, even at the longest zoom setting, backed up by super-fast autofocus and highly effective stabilization. Value ★★★★☆ It’s pricier than the F-mount 200-500mm lens but well worth the extra outlay. Canon RF 100-500mm (Image credit: Future) 5. Canon RF 100-500mm f/4.5-7.1L IS USM Not a 150-600mm - but a great option for Canon full-frame mirrorless Our expert review: Specifications Mount: Canon RF Elements/groups: 20/14 Diaphragm blades: 9 Autofocus: Dual Nano USM Stabilizer: Yes Min focus distance: 0.9-1.2m Max magnification: 0.33x Filter thread: 77mm Dimensions (WxL): 93.8x207.6mm Weight: 1530g Today's Best Deals View at Amazon View at Adorama View at Best Buy View at Target Reasons to buy + Lacks the reach of a true 150-600mm + Brilliant image quality Reasons to avoid - Disappointing AF speed on older EOS R bodies - Narrow maximum aperture The Canon RF 100-500mm f/4.5-7.1L IS USM is the first super-telephoto zoom lens for EOS R-system mirrorless cameras. This is a high-quality lens with its L-series build, and even has a heat shield coating for coping with shooting in challenging weather conditions, whether it’s hot or cold. Plus its 5-stop image stabilization will help you deliver sharp shots when shooting handheld with slower shutter speeds and in low light. It lacks the reach of a 150-600mm at its telephoto lens - but compensates for this with its widest tele setting. See our full Canon RF 100-500mm review Image 1 of 2 (Image credit: Matthew Richards/Digital Camera World) (Image credit: Matthew Richards/Digital Camera World) Swipe to scroll horizontally Features ★★★★★ There’s a smorgasbord of features packed into this lens with optical stabilization, dual Nano USM autofocus motors and a very high-end optical path. Design ★★★★★ Flourishes include a zoom ring torque adjustment, carried forward from the EF lens, and robust weather-sealed build quality. Performance ★★★★★ Autofocus performance needs one of the more recent than original EOS R bodies to get the most out of the lens, but image quality is fabulous. Value ★★★★☆ It’s pretty good value for what it is, but this lens will nevertheless make a sizeable dent in your bank balance. Sony 200-600mm (Image credit: Sony) <a href="https://www.digitalcameraworld.com/reviews/sony-fe-200-600mm-f56-63-g-oss-review" data-url="https://www.digitalcameraworld.com/reviews/sony-fe-200-600mm-f56-63-g-oss-review" target="_blank" referrerpolicy="no-referrer | 2026-01-13T09:29:41 |
https://www.digitalcameraworld.com/buying-guides/best-nd-grad-filters#section-the-quick-list | The best ND grad filters for photography | Digital Camera World Skip to main content Open menu Close main menu Digital Camera World THE HOME OF DIGITAL PHOTOGRAPHY US Edition US Canada UK Australia Subscribe Sign in View Profile Sign out Search Search Digital Camera World Cameras Accessories Tech How To Reviews Buying Guides Magazines Bokeh Face Podcast The Photography & Video Show Digital Camera Australian Camera Australian ProPhoto About Us Photography Magazines Why subscribe? Issues filled with product reviews, latest updates, expert advice and more Delivered to your Android or IOS device Every issue is packed with photo tips, kit reviews and inspiration From $12 Subscribe now Jump to: The Quick List Best hard ND grad kit Best soft ND grad kit Best budget Best premium Best magnetic Best double ND grad How to choose How we test Don't miss these Cameras The best camera for beginners: Let me show you the right camera to start your shooting journey! Lens Filters The best polarizing filters in 2026: top polarizers for landscape photographers Monitors The best monitors for photo editing: affordable and premium computer screens Tripods The best travel tripod: lightweight, stable supports for taking on the road Lenses The best protection filters for lenses in 2026: UV, skylight and clear filters Compact Cameras The best APS-C compact cameras: top image quality in your pocket DSLR Cameras The best DSLR in 2025: Chunky, classic camera designs still loved today Mirrorless Cameras The best Nikon camera: from basic beginner cameras to advanced pro models Cameras The best camera for street photography in 2026 Bridge Cameras The best bridge camera: ultra-zoom cameras for far-off subjects Digital Photo Frames The best digital photo frames: show off your shots in style Lenses The best lenses for the Sony ZV-E10 & ZV-E10 II: smart choices for vlogging and just about any other genre of video and stills photography Lenses The best Nikon lenses for DSLRs in 2026: brilliant lenses for Nikon F-mount cameras Lenses The best lenses for the Sony A6400: let me help you pick some perfect lenses for your pocket powerhouse Sony body Tripods The best tripod for photographers: give your camera a rock-steady support Popular Camera news Camera rumors Photo mag deals Photography & Video Show Cheatsheets Cameras Lenses Lens Filters The best ND grad filters in 2026: top graduated neutral density filters right now Buying guides By Ben Andrews last updated 6 January 2026 This is my pick of the best ND grads for landscape photography: get bright skies under control for a more balanced exposure When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works . (Image credit: Digital Camera World) Jump to: The Quick List Best hard ND grad kit Best soft ND grad kit Best budget Best premium Best magnetic Best double ND grad How to choose How we test Share Share by: Copy link Facebook X Whatsapp Pinterest Flipboard Share this article Join the conversation Follow us Add us as a preferred source on Google The best ND grad filters can be a landscape photographer's best friend, making it easier to achieve smooth, even exposures when the light isn't playing ball. Sick of overexposed, washed-out skies, or muddy, underexposed foregrounds? An ND grad filter is the ideal solution – and I've picked out the best ones here. Essentially, an ND grad is a piece of glass that's clear at one end and grey at the other. It's placed in front of the lens, and then by adjusting it so that the darker section of the filter covers the brighter portion of the scene, it restricts the light by several f-stops, thereby ensuring an even exposure in difficult lighting conditions. While this effect can be replicated using HDR (taking multiple exposures and merging them in post-processing), an ND grad filter gets it right in-camera. Different ND grads offer different intensities of effect, which you may want to use depending on how sharp the contrast is in the scene you're capturing. You also have other filter options: hard grads and soft grads. Hard grads have a sharp transition between light and dark – useful for straight, well-defined horizon lines – while soft grads transition more gradually, which works better for more cluttered scenes, including cityscapes or mountains. There's also the reverse ND grad filter, which has a dark section across the middle that fades upwards towards the top, and is the filter of choice for capturing sunrises and sunsets, with the sun close to the horizon. Whichever you choose, ensure you get a filter that physically fits your lens. The larger the filter, the more lens diameters it will cover and the more flexibility you'll have in positioning the transition area; larger filters tend to cost more, however. In this round-up, I've exclusively selected 100x150mm rectangular filters, or filter types that include this option, as this size offers maximum versatility for an affordable price. All these filters will deliver optical quality with little to no color cast. I've tested them out, and I'm confident you'll be happy with any filter on this list! Ben Andrews Lab Manager Ben is the Imaging Labs manager, responsible for all the testing on Digital Camera World and across the entire photography portfolio at Future. Whether he's in the lab testing the sharpness of new lenses, the resolution of the latest image sensors, the zoom range of monster bridge cameras or even the latest camera phones, Ben is our go-to guy for technical insight. He's also the team's man-at-arms when it comes to camera bags, filters, memory cards, and all manner of camera accessories – his lab is a bit like the Batcave of photography! With years of experience trialling and testing kit, he's a human encyclopedia of benchmarks when it comes to recommending the best buys. The Quick List Best hard ND grad kit 1. Lee Filters 100mm Neutral Density Grad Set - Hard View at Amazon This high-quality set of filters offers options for adding a graduation to flat-horizon shots, like seascapes, at three different stops. Read more below… Best soft ND grad kit 2. Cokin Nuances Extreme Z-Pro Soft Graduated ND Kit View at Amazon View at Amazon Made from Schott glass, this trio offers soft graduations between two and four stops, for everyday landscape shooting. Read more below… Best budget 3. Benro Master 100x150mm Glass GND View at Amazon View at Amazon View at Adorama The appealing prices in this range don’t mean any sacrifice in quality, with coatings for waterproofing and reducing color casts. Read more below… Best premium 4. Formatt Hitech Firecrest Ultra 100mm Grads Check Amazon A clever reversal of the usual manufacturing process uses bonded glass, which makes this range more rigid and scratch-resistant. Read more below… Best magnetic 5. Marumi 100x150mm Magnetic Graduated ND Filters View at Amazon View at Amazon View at Adorama View at Amazon This filter range comes in magnetic frames made by H&Y – just snap the grad onto your filter holder, then slide to adjust the horizon. Read more below… Best double grad 6. Kase Wolverine Double Grad filter View at Amazon View at Amazon View at BHPhoto Tired of swapping hard and soft grads to test which works better? This grad offers both in one filter – simply flip it upside-down! Read more below… Best ND grad filters in 2026 Why you can trust Digital Camera World Our expert reviewers spend hours testing and comparing products and services so you can choose the best for you. Find out how we test. Best hard ND grad kit (Image credit: Future) 1. Lee Filters 100mm Neutral Density Grad Set – Hard Cost-effective resin filters that maintain superb image quality Average Amazon review: ☆ ☆ ☆ ☆ ☆ Specifications Available sizes: 75x90mm, 100x150mm, 150x170mm Included densities: 1, 2 & 3 stops Available transitions: Soft, medium, hard, or extra hard Today's Best Deals View at Amazon Reasons to buy + Well priced + Excellent optical quality + light and resilient construction Reasons to avoid - Poor water and oil resistance - Resin rather than glass Unusually for high-end ND grad filters, Lee’s grads are made from polycarbonate resin rather than the more commonplace optical glass. Lee says this makes it easier to dye the tinted portion of the graduation, so that the stated density is more precise and you can position the transition line more accurately. Resin is also said to have lower intrinsic reflectivity, negating the need to apply an anti-reflective coating. If there is any disadvantage to using resin rather than glass when it comes to image quality, I couldn’t find it. Lee’s grads maintain perfect image sharpness and color neutrality, although my sample filters did produce visibly different exposure brightness, despite adjusting shutter speed appropriately for each filter. The filters do not have a hydrophobic coating, so water doesn’t bead away quite as willingly as with competing filters that feature this. This set consists of three hard grad filters, which are suitable for level horizons. particularly seascapes. The densities are rated as 0.3, 0.6, and 0.9, equivalent to one, two, and three exposure stops. Back to the top ⤴ Best soft ND grad kit (Image credit: Future) 2. Cokin Nuances Extreme Z-Pro Soft Graduated ND Kit A versatile kit that performs superbly Average Amazon review: ☆ ☆ ☆ ☆ ☆ Specifications Available sizes: 84x100mm, 100x150mm, 130x170mm Included densities: 2, 3 & 4 stops Available transitions: Soft or reverse Today's Best Deals View at Amazon View at Amazon Reasons to buy + Well priced for each filter in kit + Very good optical quality + Lovely holder Reasons to avoid - Density rating could be more accurate I’ve sampled several filters in Cokin’s top-line Nuances Extreme range, and have come away impressed every time. This kit of three 100x150mm soft grad NDs doesn’t disappoint either. Two-, three-, and four-stop densities are included, which cover most landscape shooting scenarios. Each Cokin filter is constructed from uncompromising Schott glass. Cokin also applies a water and oil-resistant coating, and it works brilliantly. I can’t fault these filters for image sharpness, either, as all three perfectly preserve maximum lens sharpness. Color tint neutrality is also top-notch, although if I'm to nitpick, the density of my sample two-stop filter was slightly darker than specified. Nuances Extreme ND grads can be had in three size options: P Series (84mm-wide), Z-Pro (100mm-wide), and X-Pro (130mm-wide). I recommend these 100mm Z-Pro filters, though, as they’re a suitable size for lenses with a filter thread up to 95mm. Back to the top ⤴ Best budget ND grad filters (Image credit: Future) 3. Benro Master 100x150mm Glass GND Benro’s Master ND grads offer unbeatable performance for the money Average Amazon review: ☆ ☆ ☆ ☆ ☆ Specifications Available sizes: 100x150mm, 150x170mm, 170x190mm Available densities: 2-5 stops (100x150mm size) Available transitions: Soft, hard, or reverse Today's Best Deals View at Amazon View at Amazon View at Adorama Reasons to buy + Class-leading optical quality + Superb water/oil-resistant coating + Neat frame & holder design Reasons to avoid - Holder a bit bulky compared with rivals Utilizing top-end German Schott B270 optical glass, Benro ’s Master Filters boast ULCA (Ultra Low Chromatic Aberration) and reflectivity below 1.5%. A waterproof multicoating is also applied to repel dirt and liquid, and it also resists scratches. Then there’s the anti-infrared coating that blocks IR and UV light to minimize the chance of unwanted color casts. It all sounds good, and thankfully, my testing of sample two-stop and four-stop filters backs it up. The tinted region has no negative impact on image sharpness and doesn’t introduce any observable color shift. Benro’s hydrophobic coating is also terrific, beading water off the filter without a trace. Benro Master Filters come in a few size variants, but I reckon the 100x150mm option is the best balance of versatility and cost. Choose from two-, three-, four-, or five-stop densities, in soft, hard, or reverse fades. The Benro system’s filter holder also deserves a mention. It’s paired with a clever filter frame that can be moved up and down within the holder by a geared wheel, enabling ultra-precise filter positioning. Back to the top ⤴ Best premium ND grad filters (Image credit: Future) 4. Formatt Hitech Firecrest Ultra 100mm Grads Providing you steer clear of water, these filters won’t disappoint Specifications Available sizes: 100x150mm Available densities: 2 & 3 stops Available transitions: Soft, hard, or reverse Today's Best Deals Check Amazon Reasons to buy + Optically flawless + Reverse-transition option + System uses a good quality holder Reasons to avoid - Only 2 and 3 stop density options - No water/oil resistance The distinctive feature of Firecrest Ultra filters is that they have their tinted coating inside the filter, sandwiched between two sheets of 1mm glass. This enhances the scratch resistance of the filter while enabling the glass to be lapped and polished so it's perfectly flat and clear. An added benefit of having two bonded sheets of glass, rather than a single pane, is greater rigidity. This manufacturing process certainly pays dividends when it comes to optical quality. My testing showed flawless image sharpness, density accuracy, and color neutrality. The only downside of sandwiching the filter coating inside the filter is that there’s no hydrophobic coating on the outside, so water droplets don’t bead away – not great when shooting a seascape. Firecrest Ultra ND grads are available in soft, hard, or reverse transitions, with the hard-edge grads offered in two- and three-stop densities. While other non-Ultra Firecrest filters can be had in smaller size options, the Ultra range only comes in this 100x150mm guise, but this is the ideal size for most users. Back to the top ⤴ Best magnetic ND grad filters (Image credit: Future) 5. Marumi 100x150mm Magnetic Graduated ND Filters Superb filters that are a pleasure to use, if slightly short on bang-per-buck Average Amazon review: ☆ ☆ ☆ ☆ ☆ Specifications Available sizes: 100x150mm Available densities: 2, 3 & 4 stops Available transitions: Soft, hard, or reverse Today's Best Deals View at Amazon View at Amazon View at Adorama View at Amazon Reasons to buy + Top-notch optical quality + Clever magnetic attachment Reasons to avoid - Relatively pricey - Density accuracy not quite as advertised Marumi’s filters stand out thanks to their magnetic filter frames (with the frames made by H&Y). When combined with Marumi’s Magnetic Filter Holder M100, the filters simply press onto the holder and detach just as easily, yet still hold securely when in use. The magnets also make it a cinch to slide the filter up and down the holder to precisely align the ND’s transition line to suit your composition. It’s a very neat system. The frame surrounds premium Schott B270 glass, coated on both sides for scratch, water, oil, and reflection resistance. I tested ND4 (two-stop) and ND16 (four-stop) hard graduated filters, with respectable results. Although the darker ND came up slightly lighter than spec, all other aspects of image quality – sharpness, color neutrality – were flawless. Marumi’s water-repelling coating is also brilliant, beading droplets as effectively as the Benro filter on this list. The Magnetic Filter System is exclusively 100mm wide – ideal for most stills photography – and you can choose from ND grads with soft, hard, or reverse transitions. All come in two-, three-, or four-stop densities. Back to the top ⤴ Best double ND grad filters (Image credit: Digital Camera World) 6. Kase Wolverine Double Grad filter This could be a game-changing ND grad Our expert review: Average Amazon review: ☆ ☆ ☆ ☆ ☆ Specifications Available sizes: 100mm square holder Available densities: 3 stops (150x100mm square) Available transitions: Soft/hard or reverse/medium Today's Best Deals View at Amazon View at Amazon View at BHPhoto Reasons to buy + Two filters in one + Top-notch quality Reasons to avoid - Limited intensity options (for now) - Not suited to ultra-wide lenses In a real "why had no one thought of this before?" moment, the Kase Wolverine Double Grad filter is a genuinely game-changing ND grad filter. Normally, when using ND grads, you need to pick whether you want to use a hard grad (a sharp transition from dark to light) or a soft grad (a more gradual one). The Wolverine Double Grad puts both of these types into a single filter, which you can adjust in the 100mm holder according to the transition you want to use. It's clever, it saves on glass and bag clutter, and most importantly of all, it works. In my testing, I was impressed with the optical performance and smooth handling of the Wolverine Double Grad Soft/Hard version, which performs well with all but the widest focal lengths. I found no color cast in Raw files, and found moving the filter up and down, while monitoring the changing image in Live View, to be highly intuitive. Read our full Kase Wolverine Double Grad review Back to the top ⤴ How to choose the best ND grad filter 1. Shape I've solely featured 100mm-wide rectangular ND grad filters, as they're large enough to suit the vast majority of compositions. You can also purchase circular screw-in grad filters, but these tend to be pretty restrictive, as the transition area is in the center of the frame. 2. Neutrality The clue is definitely in the name here. Good neutral density filters should be neutral, introducing no noticeable color casts or unwanted fuzziness to your images. 3. Density If you're buying your first ND grad filter, you'll want to consider how you're likely to use it and purchase one that's pretty flexible. If you get too low a density, you might find that overly bright skies can still be overexposed. Alternatively, if you get too dark a density, the skies will take on an overbearing, leaden appearance. 4. Material The majority of filters are made from optical-grade resin, which makes them lighter and more shatter-resistant than the glass alternatives. However, the downside is that they tend to be more prone to picking up scratches, so be sure to handle them carefully. 5. Versatility If you invest in an ND grad filter system complete with a filter holder , you then have the option of adding more filters to your line-up later. This means you could use polarizers, 'solid' ND filters , or color grads to add some extra pizazz to your images. 6. Single filters or kits? If you already have a filter system, you just need to add single filters – you don't need to buy a whole new kit all over again. But if you're just starting out, a filter kit will give you everything you need at a lower all-in price. 7. Double-check the details It's the strength and transition you need to check. There are lots of permutations! Don't get a 1-stop soft grad when you meant to get a 3-stop hard grad... Back to the top ⤴ How we test filters When we test filters, we look at both optical performance and general build quality – how robust the filter feels, how easy it is to use and how securely it attaches to the lens. We use a combination of real-world and lens testing to inform our comments in reviews and buying guides. For filters, we test light transmission levels, colour neutrality (i.e. if the filter introduces a cool or warm cast) and the impact a filter has on image quality. Find out more about how we test and review on Digital Camera World Back to the top ⤴ Round up of today's best deals Lee Filters 100mm ND Grad Set $409.63 View See all prices Cokin Nuances Extreme Z-Pro Soft $358.02 View See all prices Benro Master 100x150mm Glass GND $200 View See all prices Marumi 100x150mm Graduated Magnetic $89.95 View See all prices Kase Wolverine Double Grad $129.95 View See all prices We check over 250 million products every day for the best prices powered by Get the Digital Camera World Newsletter The best camera deals, reviews, product advice, and unmissable photography news, direct to your inbox! Contact me with news and offers from other Future brands Receive email from us on behalf of our trusted partners or sponsors By submitting your information you agree to the Terms & Conditions and Privacy Policy and are aged 16 or over. TOPICS F-Number Ben Andrews Social Links Navigation Ben is the Imaging Labs manager, responsible for all the testing on Digital Camera World and across the entire photography portfolio at Future. Whether he's in the lab testing the sharpness of new lenses, the resolution of the latest image sensors, the zoom range of monster bridge cameras or even the latest camera phones, Ben is our go-to guy for technical insight. He's also the team's man-at-arms when it comes to camera bags, filters, memory cards, and all manner of camera accessories – his lab is a bit like the Batcave of photography! With years of experience trialling and testing kit, he's a human encyclopedia of benchmarks when it comes to recommending the best buys. Back To Top Read more The best variable ND filters: fader filters for videography and photography The best polarizing filters in 2026: top polarizers for landscape photographers The best infrared filters in 2026: create surreal images in color and black & white The best close-up filters: macro photography on a budget The best diffusion filters: soft-focus, low-contrast filters for the cinematic look The best protection filters for lenses in 2026: UV, skylight and clear filters Latest in Lens Filters I’ve never seen bokeh like this before! This photographer DIYed a filter for a crazy spinning bokeh effect Image quality purists will tell you otherwise, but this is why I use a UV filter on all of my lenses Circular polarizers are fantastic, but dark. This new filter lets in more light than most – and is made to be used with gloves There's one photo accessory I'm determined to get on Prime Day, and you should too PolarPro Warp review: This bizarre filter hides a trifecta of special effects. Can it cure boring photos? Stop putting Vaseline on camera lenses! This new filter has a dreamy diffusion effect with a sharp center – and it’s just one of the unique options in this magnetic set Latest in Buying guides These are my top 12 photography books published in 2025 The best lenses for the Nikon ZR: I choose the top lenses to give you a truly cinematic experience The best lenses for the Canon EOS R50 V: Geared for video, this camera deserves the right lenses for making movies The best lenses for the Canon EOS R6 Mark III: I pick out the top choices for kitting out your R6 III with great glass, at sensible prices The best lenses for the Fujifilm X-T30 III: find the ideal lenses for this compact, lightweight, and competitively priced camera These Black Friday deals on a MacBook Pro or Mac mini are too good to miss! LATEST ARTICLES 1 I took photos of 36 electric boxes in Buenos Aires and made some decent dough from them. Odd subjects often pay better than postcard views 2 100 winning portraits turn Britain's streets into a nationwide photography exhibition 3 Premium Canon glass, pocket-sized price: $170 off the Canon Zoom Monocular 4 Rugged phones completely changed my life in 2025 – here's why these big beasts have become my most trusted travelling companions 5 DJI Osmo Mobile 8 review: A pro-grade phone gimbal that keeps up with ambitious creators without breaking the bank Digital Camera World is part of Future US Inc, an international media group and leading digital publisher. Visit our corporate site . Add as a preferred source on Google Terms and conditions Contact Future's experts Privacy policy Cookies policy Advertise with us About us Accessibility Statement Careers © Future US, Inc. Full 7th Floor, 130 West 42nd Street, New York, NY 10036. Close Please login or signup to comment Please wait... Login Sign Up | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/jira/solutions/program-management#tab-e4844879-4e34-405b-a9a9-9a9064624462 | 计划管理 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Atlassian 在 2025 年 Gartner 协作工作管理魔力象限™ 中被评为领导者！ 了解更多 Jira 为计划管理助力 使用 Jira 简化、精简、交付 了解 Jira 如何帮助您和您的团队将宏伟目标转化为可实现的项目。 免费获取 Jira 加入我们 30 多万个客户的行列，携手 Atlassian 赋能团队协作 为什么使用 Jira 进行计划管理？ 克服复杂性 无论有多少团队参与其中，即使是最艰巨的战略计划，也要分解成可实现的小步骤。 驾驭依赖关系 在潜在的中断和不确定性影响团队工作之前，提前做好准备。 全面的可见性 查看和组织各团队的工作，以便更好地管理资源配置，做出明智的战略决策。 专为计划管理而设计的模板 适用于各类计划、项目和举措的可定制模板。 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 确定任务的优先次序，管理团队工作量，跟踪工作从规划到完成的整个过程。 开始使用 顶层规划 为您的团队提供清晰、实时的视图，以便进行协作、安排和调整战略目标。 开始使用 流程规划 让您的团队不再重复流程。对各种流程中的步骤进行分类，以便您和您的团队能够快速识别未完成的任务。 开始使用 甘特图 一款强大的可视化工具，用于跟踪工作和避开障碍。概述项目工期，指明里程碑并绘制依赖关系。 开始使用 个人任务跟踪器 跟踪个人任务，如电子邮件分类、会议准备和费用管理。 开始使用 计划和启动项目，全部从 Jira 中进行 规划 需求不断变化？没有关系 分析项目并自信地与利益相关者沟通，明确进度和优先事项。 执行和跟踪 协调工作，简化流程 跟踪项目，映射依赖关系，建立跨团队的审批工作流，并确保目标如期实现。 报告和结果 完善工作流程 有了触手可及的项目摘要，您就能更明智地制定计划，并随时掌握各项举措和项目的进展情况。 计划面板公开测试版 计划或季度规划的新界面 计划面板公开测试版 计划或季度规划的新界面 通过简单的拖放式计划功能，为下个季度规划多个团队的工作。 了解更多 集成您最喜欢的所有工具 将您的工具与 Jira 巧妙地集成，而无需在平台之间进行上下文切换。 查看更多集成 计划管理资源 浏览免费教程、文章和指南以了解更多信息。 敏捷教练 将数十年的敏捷实践提炼成简单易读的课程。 了解更多 项目管理指南 帮助您计划和管理项目的分步说明。 了解更多 协调业务和技术团队 了解如何打破孤岛，开展合作以便创造更好的产品。 阅读博客 转换工作方式 免费获取 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://www.drupal.org/node/3218720 | Contributed module, theme, or distribution maintainer | Drupal.org Skip to main content Skip to search Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see ? Yes, please No, do not track me Drupal.org home Discover Drupal Drupal Core Drupal CMS Drupal AI Case Studies Drupal for Government Drupal for Higher Education Drupal for Nonprofit Drupal for eCommerce Drupal for FinTech Drupal for Healthcare Drupal for Enterprise Drupal for Retail Drupal for Travel & Tourism Build with Drupal Download Drupal Documentation Getting started Local Development Guide Developer Resources Drupal CMS User Guide Drupal User Guide API Modules Themes Distributions Issue queues Security Advisories Partners & Services Find a Drupal Certified Partner Become a Drupal Certified Partner Find a Hosting Provider Find a Migration Partner Find Training Drupal Steward Community About the Community How to Contribute DrupalCon Events Jobs / Careers News & Blogs Forum Slack Newsletters Drupal Swag Shop Support Drupal The Drupal Association Donate Become a Partner Become a Ripple Maker Become an Organization Member Drupal Swag Shop Get Started Try Drupal CMS Try Hosting Return to content Search form Search Log in Create account Community Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options. Migration Resource Center Contributor guide Find your role Contributed module, theme, or distribution maintainer Maintain or co-maintain the software and design for a contributed module , theme , or distribution project on drupal.org. Impact: Contributed modules, themes, and distributions allow Drupal users to add new functionality and design to their sites, beyond that offered by the Drupal core software. Drupal core and web technology are always evolving, and users of the projects will inevitably find bugs and think of suggestions for new features. For that reason, every project needs to have one or more maintainers to update the project's software and respond to issues. Accountable for: Responding to issues that are submitted in the project's issue list: politely, constructively, and in a timely manner Reviewing and committing code changes Responding promptly and confidentially to security issues Updating the project's software when Drupal core evolves Maintaining documentation for the project Finding co-maintainers to spread the work around Exiting gracefully when you are no longer able or willing to maintain the project For more details, see the guide to managing a contributed project . How to get started: Participate in the issue queue for an existing module, theme, or distribution project (see "Tasks this role performs" on this page): Triage issues Provide patches Review patches Once you have been participating for a while, and are familiar with the project's source code, create an issue in the project to request co-maintainer status. Skills required: Product management Project management Tasks this role performs: Create a Drupal 11 compatibility merge request Handle or refer a support request in an issue Identify duplicate issues Manually test a proposed fix for an issue Review a merge request Triage an issue report Write an automated test for an issue Duration: ongoing Skills optionally used: CSS coding Drupal theming / theme building Graphic design HTML coding JavaScript coding/programming PHP coding/programming Technical writing (English) Usability and user interface design Writing automated tests Contribution areas Contributed modules, themes, and distributions Contribute to improving modules, themes, and distributions. Read more about contributing to this area . Help improve this page Create an issue describing the problem. Need help deciding how to contribute? Visit the Community landing page to learn more about the Drupal community, or start at the top of the Contributor Guide to find roles and tasks organized by skills and community areas. Need help completing a task? Check out the Getting help with contributing section. News items News Planet Drupal Social media Sign up for Drupal news Security advisories Jobs Our community Community Services , Training & Hosting Contributor guide Groups & meetups DrupalCon Code of conduct Documentation Documentation Drupal Guide Drupal User Guide Developer docs API.Drupal.org Drupal code base Download & Extend Drupal core Modules Themes Distributions Governance of community About Web accessibility Drupal Association About Drupal.org Terms of service Privacy policy Drupal is a registered trademark of Dries Buytaert . | 2026-01-13T09:29:41 |
https://www.facebook.com/recover/initiate/?ars=facebook_login&cancel_lara_pswd=0&next=https%3A%2F%2Fwww.facebook.com%2Fdialog%2Fsend%3F_path%3Dsend%26app_id%3D860047027665875%26client_id%3D860047027665875%26redirect_uri%3Dhttps%253A%252F%252F10web.io%252Fblog%252Fvps-hosting-vs-dedicated-hosting%252F%26display%3Dpage%26link%3Dhttps%253A%252F%252F10web.io%252Fblog%252Fvps-hosting-vs-dedicated-hosting%252F%26from_login%3D1 | Facebook 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back | 2026-01-13T09:29:41 |
https://pt-br.facebook.com/reg/?entry_point=login&next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT3_jrBST8nb5JK4n8SuC7I3odI03dggP1O-lLIl6bZeBAC_fJAZbG0wge2jfg3OYutC9T2ysL1NtgN9-JAjQNUdYSGz3aCK2FZM92e_MU5JfsRRkAB1cAJxg-KtLMpj_k4mcKaujoV0_Oqh | Facebook Comece a usar o Facebook Crie uma conta para se conectar com amigos, familiares e comunidades de pessoas com os mesmos interesses que você. Nome Nome Sobrenome Data de nascimento Gênero Selecione seu gênero Número de celular ou email Número de celular ou email Você poderá receber notificações enviadas por nós. Saiba por que pedimos suas informações de contato Senha Senha As pessoas que usam nosso serviço podem ter carregado suas informações de contato no Facebook. Saiba mais . Ao tocar em Enviar , você concorda em criar uma conta e em seguir os Termos , a Política de Privacidade e a Política de Cookies do Facebook. A Política de Privacidade descreve como podemos usar as informações que coletamos quando você cria uma conta. Por exemplo, usamos essas informações para fornecer, personalizar e melhorar nossos produtos, incluindo anúncios. Enviar Já tenho uma conta Português (Brasil) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español Mais idiomas... Cadastre-se Entrar Messenger Facebook Lite Vídeo Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Mais conteúdo da Meta AI Instagram Threads Central de Informações de Votação Política de Privacidade Central de Privacidade Sobre Criar anúncio Criar Página Desenvolvedores Carreiras Cookies Escolhas para anúncios Termos Ajuda Upload de contatos e não usuários Meta © 2026 | 2026-01-13T09:29:41 |
https://citl.illinois.edu/node/82 | Teachers Ranked as Excellent | Center for Innovation in Teaching & Learning Skip to main content University of Illinois Urbana-Champaign Center for Innovation in Teaching & Learning Search About Who We Are Row Wrapper Column Overview Current Events Special Events Careers Column CITL Directory CITL Fellows How We Can Help How We Can Help Row Wrapper Column Overview Search by Audience & Service Enrich Your Teaching Enhance Your Teaching Skills Promote Student Engagement Universal Design for Learning Make Your Course Accessible (MYCA) Foster Inclusion Graduate Academy for College Teaching Student Resources Achieve Academic Success Take Care of Your Wellbeing Internships Column Create Online Courses Develop a New Program with CITL Develop a New Course with CITL Update an Existing Course Access Self-Service Kits Instructional Support Broadcast & Record Events Exam Scoring Services Slate CRM Systems Column Collect & Analyze Data Finding Data Survey Research Consulting & Training I-STEM Placement & Proficiency Current Cutoffs P&P FAQs Ask a Question Explore Our Spaces Explore Our Spaces Row Wrapper Column Overview Innovation Studio X3 Studio CITL IDEASpace Media Recording Spaces Innovate With Us Innovate With Us Row Wrapper Column Overview Explore, Develop, and Pilot New Strategies Learn and Apply AI & XR Solutions Generative Artificial Intelligence Immersive Technology Teaching Evaluation Teaching Evaluation Row Wrapper Column Overview Campus Teaching Evaluation System Self Evaluation Feedback on the Learning Experience (FLEX) Informal Early Feedback (IEF) FLEX FAQ Focus Groups Teachers Ranked as Excellent Column Longitudinal Teaching Profiles Share Your Experience Share Your Experience Row Wrapper Column Overview CITL Podcast Instructor Voices Student Voices Newsletter Archive Ask a Question Teachers Ranked as Excellent Home Campus Teaching Evaluation System Feedback on the Learning Experience (FLEX) Teachers Ranked as Excellent The List of Teachers Ranked as Excellent by Their Students was part of the ICES system which is now retired. To learn more about how FLEX will inform teaching awards, please consult the provost’s website . Lists generated under the ICES system were created each semester based on student ratings of instruction. A couple of points to note: In summer 2007 we dropped "Incomplete" from the list name. Criteria for making the list remain the same. Until the list based on Spring 2000 data, the title of the Incomplete List contained the semester in which the list was published, not the semester that the list is reporting on. Beginning with the Incomplete List published in the Fall 2000 semester (based on Spring 2000 data), the title of the list now contains the semester from which the data was obtained. For this reason, there are two "Spring 2000" lists, one based on Fall 1999 data and another based on Spring 2000 data. List for 2025 (based on Spring, Summer, and Fall 2025 and Winter 2025-2026 data) [pdf] List for 2024 (based on Spring, Summer, and Fall 2024 and Winter 2024-2025 data) [pdf] List for 2023 (based on Spring, Summer, and Fall 2023 and Winter 2023-2024 data) [pdf] List for 2022 (based on Spring, Summer, and Fall 2022 and Winter 2022-2023 data) [pdf] List for 2021 (based on based on Spring, Summer, and Fall 2021 and Winter 2021-2022 data) [pdf] List for 2020 (based on based on Spring, Summer, and Fall 2020 and Winter 2020-2021 data) [pdf] List for 2019 (based on based on Spring, Summer, and Fall 2019 and Winter 2019-2020 data) [pdf] List for 2018 (based on based on Spring, Summer, and Fall 2018 and Winter 2018-2019 data) [pdf] List for 2017 (based on based on Spring, Summer, and Fall 2017 data) [pdf] List for 2016 (based on based on Spring, Summer, and Fall 2016 data) [pdf] List for 2015 (based on based on Spring, Summer, and Fall 2015 data) [pdf] List for 2014 (based on based on Spring, Summer, and Fall 2014 data) [pdf] List for 2013 (based on based on Spring, Summer, and Fall 2013 data) [pdf] List for 2012 (based on based on Spring, Summer, and Fall 2012 data) [pdf] List for 2011 (based on based on Spring, Summer, and Fall 2011 data) [pdf] List for 2010 (based on based on Spring, Summer, and Fall 2010 data) [pdf] List for 2009 (based on based on Spring, Summer, and Fall 2009 data) [pdf] List for 2008 (based on based on Spring, Summer, and Fall 2008 data) [pdf] List for 2007 (based on based on Spring, Summer, and Fall 2007 data) [pdf] Incomplete List for 2006 (based on based on Spring, Summer, and Fall 2006 data) [pdf] Incomplete List for 2005 (based on based on Spring, Summer, and Fall 2005 data) [pdf] Incomplete List for 2004 (based on based on Spring, Summer, and Fall 2004 data) [pdf] Incomplete List for 2003 (based on based on Spring, Summer, and Fall 2003 data) [pdf] Incomplete List for 2002 (based on based on Spring, Summer, and Fall 2002 data) [pdf] Incomplete List for 2001 (based on based on Spring, Summer, and Fall 2001 data) [pdf] Incomplete List for 2000 (based on based on Spring, Summer, and Fall 2000 data) [pdf] NOTE: In previous years, shown below, the Incomplete List has always been published one semester after the data was collected. In the past, it also received the name from the semester in which it was published. Beginning with the Incomplete List published in the Fall 2000 semester (Spring 2000 data), the title of the list is now synonymous with the semester in which the data was obtained. Therefore, there are actually two "Spring 2000" lists--one from the Fall 1999 data (below) and one from the Spring 2000 data (above). Incomplete List for 2000 (based on Fall 1999 data) [pdf] Incomplete List for 1999 (based on Fall 1998 data) [pdf] Incomplete List for 1998 (based on Fall 1997 data) [pdf] Incomplete List for 1997 (based on Fall 1996 data) [pdf] Incomplete List for 1996 (based on Fall 1995 data) [pdf] Incomplete List for 1995 (based on Fall 1994 data) [pdf] Incomplete List for 1994 (based on Fall 1993 data) [pdf] Got a Vision? We'll help you make it happen. Get in touch Center for Innovation in Teaching & Learning 505 Armory Avenue | Champaign, IL 61820 Phone: 217.333.1462 Email: citl-info@illinois.edu CITL About How We Can Help Innovate With Us Teaching Evaluation Calendar Contact Us Programs Illinois Online Illinois Remote Explore Campus University Admissions Careers at Illinois University News Visit Campus Connect with Illinois University Alumni Giving at Illinois University Calendars University Directory Access University Resources Emergency Services McKinley Health Center Connie Frank CARE Center University Library About Cookies Privacy Policy Copyright Accessibility | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/software/jira/templates/design | 设计模板 | Jira 模板库 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Jira 模板 Open and close the navigation menu 分类 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 项目管理模板 免费获取 分类 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 项目管理模板 设计模板 使用 Jira 提升您的设计工作流。借助为设计团队预先构建的可自定义模板，可以轻松开始工作。 项目管理 管理用于完成业务项目的活动。 网络设计流程 在整个设计工作流中，让团队保持一致。 设计服务管理 管理并跟踪您的所有设计请求。 资产创造 简化资产请求，让您的团队可以专注于创建。 设计资源 适用于设计团队的 Jira 发掘设计团队的敏捷性。详细了解 Jira 如何帮您简化工作。 了解更多 通过自动化机制来完成项目 专注于重要事务，剩下的事情交给自动化机制完成。创建团队的自定义规则，或者通过我们的预设自动化功能快速开始。 探索自动化 连接您最喜欢的工具 利用 500 多种集成实现无缝工作，借助 3,000 多个其他扩展来打造团队的完美流程。 探索应用市场 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://www.linkedin.com/products/coachhub--the-digital-coaching-platform/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click#main-content | CoachHub - The digital coaching platform | LinkedIn Skip to main content LinkedIn CoachHub - The digital coaching platform in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in CoachHub - The digital coaching platform AI-Powered Coaching Software by CoachHub - The digital coaching platform See who's skilled in this Add as skill Learn more Report this product About CoachHub is the global leader in digital coaching. We enable organizations to deliver personalized, scalable coaching programs that drive measurable business impact across the workforce. Coaching Solutions Designed for Scale ✔️CoachHub Individual: Support long-term growth by giving employees access to world-class business coaches. ✔️CoachHub Executive™: Help senior leaders turn complexity into clarity and vision into results. ✔️CoachHub Collective: Build stronger teams through expert-led group coaching that accelerates collaboration and problem-solving. ✔️AIMY™: Our pioneering AI coach makes coaching scalable, measurable and accessible across the organization. The Business Impact ✔️Companies that partner with CoachHub see: ✔️Higher employee engagement and retention ✔️Measurable improvements in productivity and performance ✔️Stronger leadership pipelines and employer brand Media Products media viewer No more previous content Transform People and Organizations Coaching can be life-changing. But don't just take it from us – hear it first-hand from some of our customers. What if you could unlock meaningful experiences at work, empower employees to embrace change and bring out the best in your leaders? Transform your teams through digital coaching with CoachHub. Get started today at coachhub.com. Building Future-Ready Leaders Discover how Schneider Electric revolutionized its leadership development strategy through a global digital coaching program in partnership with CoachHub. In this powerful case study, you'll hear firsthand from Schneider Electric leaders in North America as they share the impact of scaling personalized coaching to over 6,000 managers. #LeadershipDevelopment #DigitalCoaching #CoachHub #SchneiderElectric #HRInnovation #FutureOfWork #CaseStudy AIMY™: the AI Coach for the global workforce Provide employees across all career levels with a personalized, goal-oriented AI coach. Experience the power of our coaching programs Leverage our science-backed coaching framework to upskill your workforce and transform your organization. Make Collective Intelligence Your Superpower Build a culture of collaboration to multiply your workforce potential with CoachHub Collective No more next content Featured customers of CoachHub - The digital coaching platform The Coca-Cola Company Food and Beverage Services 8,635,710 followers Generali Insurance 570,803 followers Atlas Copco Group Machinery Manufacturing 192,115 followers Booking.com Software Development 1,101,962 followers Virgin Atlantic Airlines and Aviation 432,418 followers BNP Paribas Banking 1,870,442 followers Schneider Electric Automation Machinery Manufacturing 5,289,556 followers ENGIE Renewable Energy Power Generation 1,070,536 followers Danone Food and Beverage Manufacturing 3,767,250 followers Show more Show less Similar products LinkedIn Learning AI-powered Coaching LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software LinkedIn Interview Prep AI LinkedIn Interview Prep AI AI-Powered Coaching Software AI Resume Builder AI Resume Builder AI-Powered Coaching Software MOBILITY MOBILITY AI-Powered Coaching Software Exponent Practice Exponent Practice AI-Powered Coaching Software Yoodli AI Roleplays Yoodli AI Roleplays AI-Powered Coaching Software Sign in to see more Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:41 |
https://support.microsoft.com/en-us/office/get-started-in-updates-c03a079e-e660-42dc-817b-ca4cfd602e5a | Get started in Updates - Microsoft Support Related topics × Updates app Updates app in Teams Get started Managing the Updates app Automate your workflows FAQ Skip to main content Microsoft Support Support Support Home Microsoft 365 Office Teams support Topics Meetings Chat Notifications & settings Teams & channels Calls & devices Files Apps & services Quick start Chat Group chat Notifications Teams Channels Calls Files Apps Loop components What's new Resources Video training Troubleshoot Here in Teams Accessibility Teams features by platform Microsoft Teams (free) Community forums Tech community blog Instructor-lead training For admins and IT pro For Education More Buy Microsoft 365 All Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Deals Small Business Support Software Software Windows Apps AI Outlook OneDrive Microsoft Teams OneNote Microsoft Edge Moving from Skype to Teams PCs & Devices PCs & Devices Computers Shop Xbox Accessories VR & mixed reality Certified Refurbished Trade-in for cash Entertainment Entertainment Xbox Game Pass Ultimate PC Game Pass Xbox games PC games Business Business Microsoft Security Dynamics 365 Microsoft 365 for business Microsoft Power Platform Windows 365 Microsoft Industry Small Business Developer & IT Developer & IT Azure Microsoft Developer Microsoft Learn Support for AI marketplace apps Microsoft Tech Community Microsoft Marketplace Marketplace Rewards Visual Studio Other Other Microsoft Rewards Free downloads & security Education Gift cards Licensing Unlocked stories View Sitemap Search Search for help No results Cancel Sign in Sign in with Microsoft Sign in or create an account. Hello, Select a different account. You have multiple accounts Choose the account you want to sign in with. Related topics Updates app Updates app in Teams Get started Managing the Updates app Automate your workflows FAQ Get started in Updates Applies To Teams Microsoft Teams Welcome to Updates, an out-of-the-box app that allows you to create, submit, and review updates. People can easily see their employee updates, check-ins, and reports in one place to make sure the team is on track for success, whether those are recurring processes that happen on a regular basis or in-the-moment updates that might be needed at any time. Whether on a desktop or mobile device, workers are alerted in the flow of work and can easily complete and submit updates, saving everyone time and energy. Desktop Mobile Open the Updates app You’ll find Updates on the left side of Teams with other apps. Select it to start sending and receiving updates. If you don’t see it there, select + Apps on the left side of Teams and search for Updates . Request an update From the app, you can request your teammates to update their work status by requesting an update: Choose one of our recommended Templates that complement your everyday updates. If you choose a Template, preview the contents, or select Use template . You can select Explore all templates for more templates and choose Start from blank for anything in-between. Configure the update request name, adjust and/or add any questions to the template in Edit form . Assign users as Submitters if they need to complete and add content to the update. Assign users as Viewers if they can see and track update progress and the details of the submissions; Decide if Submitters are required to attach files and select Set due date and recurrence at specific times. Select Publish . For Submitters , the update request appears in the Needing your updates section on the homepage. If you make an update request, you can add a due date, a time, and the status of completion. For Viewers , update request overview will appear in the Review updates section. Manage update requests Update requests can be edited and can be made available by Assigners if they’re needed and made unavailable if they’re not. Select My requests on the homepage. Under Actions , select More options (...) . Disable makes the request not available for use, Enable makes the request active and available for use, and Edit allows you to edit the request. Submit an update Submitters can complete and add content to the update requests that have been assigned to them. Go to Updates app homepage and choose any one of the assigned requests under Needing your updates . Once you’ve added all your information and attachments, select Submit . You can also Submit a quick update to your teammates: Select Quick update in the top right corner of the app. Add your content and specify people you want to submit the update to as Viewers . Select Submit . View an update Viewers can keep up to date with the progress of updates and view the details of submitted updates. Go to Updates app homepage and navigate to Review updates . Review the submission status for each request briefly. Choose a card to see all updates from that specific request. Note: Choosing cards will display all the updates from that specific request, in order of submission, and in relation to each due date if it's a recurring request. Selecting a specific request shows the full details of the submission. Select Customize to specify what type of update data to be highlighted. Choose an update to see the details and attachments of that specific submission, or switch viewing modes to view submission content for a specific question. Create, send, and receive updates in chat or channel From your desktop, enter any chat or channel conversation and request an update from the Update app message extension. You can assign which members in current chat or channel as Submitters and Viewers. Enter your desired team chat or channel. Select More options (+) next to the send message button. Choose one of the Templates that complements your everyday updates. If you choose a template, preview the Contents, or select Use template. Configure the update request name, adjust and/or add any questions to the template in Edit form . By default, everyone in the team chat or channel are assigned as Submitters and Viewers . You can choose to expand the list and make adjustment; Decide if Submitters are required to attach files and select Set due data and recurrence at specific times. Select Publish . The Update app message extension also allows people to submit updates. Enter your desired team chat or channel conversation. Select More options (+) next to the send message button. Select Updates app. Choose or review Any assigned request created from this team chat or channel. Note: If there's already an update request card in the chat or channel and you have been assigned as a Submitter, select the card to submit a response. If you have been assigned a Viewer role, select the card to view the submissions. The update request that is created or update submitted will appear in the group chat or channel as a card allowing Submitters to submit an update from it or Viewers to view the submission. Open the Updates app You’ll find Updates in Teams on the bottom of your mobile screen. Select … More , and it should appear in the app list. If it is not in the list, click + Add app at the end of the app list and search for Updates . See your updates In Updates, the Submit tab displays updates that need to be submitted, and the Review tab displays updates you can view. Each person has Scheduled and General updates to submit or view. Scheduled updates have been assigned a due date. General updates have yet to include a due date but are available for in the moment events such as facility inspections, incident reports, and more. People can request, submit, and view updates. If it’s your first-time using Updates, don’t worry, we’ll show you the process of staying up to date with your team and give you some tips on how to use the app. Request an update Update requests can only be created from the desktop app. To start collecting updates from your team, click on the Desktop tab above and follow the steps there. Manage update requests Managing update requests can only be done on the desktop app. To begin editing, click on the Desktop tab above and follow the steps. Submit an update Submitters can complete and add content to update requests that have been assigned to them. Select the Submit tab at the top of the app. Choose an update request in Scheduled or General . Once you’ve added all your information and attachments, select Submit . All your submitted updates in Your Submissions , which is located below the Scheduled and General sections. In the Submit tab, selecting See all will display your assigned updates that can’t fit in the Scheduled and General sections. View an update Viewers can keep up to date with the progress of updates and view the details of submitted updates. Select the Review tab at the top of the app. Select a card to see updates from that specific template. Note: Selecting cards will display all updates from that specific template, in order of submission, and in relation to each due date if it’s a recurring update. Clicking on a specific update will display the full details of the submission. Choose an update located beneath Received to see the details of that specific submission. Updates listed under Scheduled will showcase each template’s Submission rate and total number that have been Submitted and are Unsubmitted . Updates under General will showcase the number of Submissions and New submissions . In the Review tab, selecting See all will display all the Scheduled and General updates. Send and receive updates in chat From your mobile device, submit and receive updates from the message extension. Enter your desired team chat or channel. Click + in the bottom left corner of the compose bar. Select Updates app. Choose your desired update request. Add your information and add Viewers if necessary. Select Submit . The update appears in the group chat or channel as a card allowing Viewers to view the submission. If there's already an Update card in the Chat or Channel and you have been assigned as a Submitter , select the card to submit a response directly for that update. If you have been assigned as a Viewer , select the card to view the submissions. Want more? Automate your workflows in Updates Managing the Updates app Explore the Updates Lookbook For IT admins Manage the Updates app for your organization in Microsoft Teams SUBSCRIBE RSS FEEDS Need more help? Want more options? Discover Community Explore subscription benefits, browse training courses, learn how to secure your device, and more. Microsoft 365 subscription benefits Microsoft 365 training Microsoft security Accessibility center Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge. Ask the Microsoft Community Microsoft Tech Community Windows Insiders Microsoft 365 Insiders Was this information helpful? Yes No Thank you! Any more feedback for Microsoft? Can you help us improve? (Send feedback to Microsoft so we can help.) What affected your experience? Resolved my issue Clear instructions Easy to follow No jargon Pictures helped Other Didn't match my screen Incorrect instructions Too technical Not enough information Not enough pictures Other Any additional feedback? (Optional) Submit feedback By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement. Thank you for your feedback! × What's new Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot for organizations Copilot for personal use AI in Windows Explore Microsoft products Windows 11 apps Microsoft Store Account profile Download Center Microsoft Store support Returns Order tracking Certified Refurbished Microsoft Store Promise Flexible Payments Education Microsoft in education Devices for education Microsoft Teams for Education Microsoft 365 Education How to buy for your school Educator training and development Deals for students and parents AI for education Business Microsoft Security Dynamics 365 Microsoft 365 Microsoft Power Platform Microsoft Teams Microsoft 365 Copilot Small Business Developer & IT Azure Microsoft Developer Microsoft Learn Support for AI marketplace apps Microsoft Tech Community Microsoft Marketplace Marketplace Rewards Visual Studio Company Careers About Microsoft Company news Privacy at Microsoft Investors Diversity and inclusion Accessibility Sustainability English (United States) Your Privacy Choices Opt-Out Icon Your Privacy Choices Your Privacy Choices Opt-Out Icon Your Privacy Choices Consumer Health Privacy Sitemap Contact Microsoft Privacy Manage cookies Terms of use Trademarks Safety & eco Recycling About our ads © Microsoft 2026 | 2026-01-13T09:29:41 |
https://www.linkedin.com/products/hubbedin-ai-resume-builder/#main-content | AI Resume Builder | LinkedIn Skip to main content LinkedIn HubbedIn in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in AI Resume Builder AI-Powered Coaching Software by HubbedIn See who's skilled in this Add as skill Try now Report this product About HubbedIn's Resume Builder is an AI-powered tool designed to simplify the resume creation process. It assists job seekers in crafting professional resumes effortlessly, offering personalized suggestions and rephrasing sentences to meet specific job requirements. Our AI tool aims to elevate job seekers' applications by ensuring your resumes stand out and accurately reflect your achievements and skills. Similar products LinkedIn Learning AI-powered Coaching LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software LinkedIn Interview Prep AI LinkedIn Interview Prep AI AI-Powered Coaching Software CoachHub - The digital coaching platform CoachHub - The digital coaching platform AI-Powered Coaching Software MOBILITY MOBILITY AI-Powered Coaching Software Exponent Practice Exponent Practice AI-Powered Coaching Software Yoodli AI Roleplays Yoodli AI Roleplays AI-Powered Coaching Software Sign in to see more Show more Show less HubbedIn products AI Video Interviewer AI Video Interviewer Video Interview Software Find a Hiring Manager Find a Hiring Manager AI-Powered Coaching Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/jira/solutions/program-management#tab-8f8206b2-67a9-411e-b687-b245687cb154 | 计划管理 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 Atlassian 在 2025 年 Gartner 协作工作管理魔力象限™ 中被评为领导者！ 了解更多 Jira 为计划管理助力 使用 Jira 简化、精简、交付 了解 Jira 如何帮助您和您的团队将宏伟目标转化为可实现的项目。 免费获取 Jira 加入我们 30 多万个客户的行列，携手 Atlassian 赋能团队协作 为什么使用 Jira 进行计划管理？ 克服复杂性 无论有多少团队参与其中，即使是最艰巨的战略计划，也要分解成可实现的小步骤。 驾驭依赖关系 在潜在的中断和不确定性影响团队工作之前，提前做好准备。 全面的可见性 查看和组织各团队的工作，以便更好地管理资源配置，做出明智的战略决策。 专为计划管理而设计的模板 适用于各类计划、项目和举措的可定制模板。 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 顶层规划 流程规划 甘特图 个人任务跟踪器 项目管理 确定任务的优先次序，管理团队工作量，跟踪工作从规划到完成的整个过程。 开始使用 顶层规划 为您的团队提供清晰、实时的视图，以便进行协作、安排和调整战略目标。 开始使用 流程规划 让您的团队不再重复流程。对各种流程中的步骤进行分类，以便您和您的团队能够快速识别未完成的任务。 开始使用 甘特图 一款强大的可视化工具，用于跟踪工作和避开障碍。概述项目工期，指明里程碑并绘制依赖关系。 开始使用 个人任务跟踪器 跟踪个人任务，如电子邮件分类、会议准备和费用管理。 开始使用 计划和启动项目，全部从 Jira 中进行 规划 需求不断变化？没有关系 分析项目并自信地与利益相关者沟通，明确进度和优先事项。 执行和跟踪 协调工作，简化流程 跟踪项目，映射依赖关系，建立跨团队的审批工作流，并确保目标如期实现。 报告和结果 完善工作流程 有了触手可及的项目摘要，您就能更明智地制定计划，并随时掌握各项举措和项目的进展情况。 计划面板公开测试版 计划或季度规划的新界面 计划面板公开测试版 计划或季度规划的新界面 通过简单的拖放式计划功能，为下个季度规划多个团队的工作。 了解更多 集成您最喜欢的所有工具 将您的工具与 Jira 巧妙地集成，而无需在平台之间进行上下文切换。 查看更多集成 计划管理资源 浏览免费教程、文章和指南以了解更多信息。 敏捷教练 将数十年的敏捷实践提炼成简单易读的课程。 了解更多 项目管理指南 帮助您计划和管理项目的分步说明。 了解更多 协调业务和技术团队 了解如何打破孤岛，开展合作以便创造更好的产品。 阅读博客 转换工作方式 免费获取 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://ftp.gnu.org/old-gnu/gictionary-0.43/?C=N;O=D | Index of /old-gnu/gictionary-0.43 Index of /old-gnu/gictionary-0.43 Name Last modified Size Description Parent Directory - uncompressed/ 2003-08-02 07:35 - Apache/2.4.52 (Trisquel_GNU/Linux) Server at ftp.gnu.org Port 443 | 2026-01-13T09:29:41 |
https://support.microsoft.com/sv-se/microsoft-store-and-billing | Microsoft Store & faktureringshjälp Gå till huvudinnehåll Microsoft Support Support Support Startsida Microsoft 365 Office Produkter Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows mer... Enheter Surface Datortillbehör Xbox PC-spel HoloLens Surface Hub Maskinvarugarantier Konto och fakturering Konto Microsoft Store & faktureringshjälp Resurser Nyheter Community-forum Microsoft 365 administratörer Portal för småföretag Utvecklare Utbildning Rapportera ett supportbedrägeri Produktsäkerhet Mer Köp Microsoft 365 Hela Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Specialerbjudanden Små företag Support Programvara Programvara Windows-appar AI OneDrive Outlook Byta från Skype till Teams OneNote Microsoft Teams Datorer och enheter Datorer och enheter Köp Xbox Tillbehör Underhållning Underhållning Xbox Game Pass Ultimate Xbox och spel PC-spel Företag Företag Microsoft Security Azure Dynamics 365 Microsoft 365 för företag Microsoft Industry Microsoft Power Platform Windows 365 Utvecklare och IT Utvecklare och IT Microsoft Developer Microsoft Learn Stöd för AI-marknadsappar Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Andra Andra Microsoft Rewards Kostnadsfria nedladdningar och säkerhet Utbildning Presentkort Licensiering Visa webbplatskarta Sök Sök efter hjälp Inga resultat Avbryt Logga in Logga in med Microsoft Logga in eller skapa ett konto. Hej, Välj ett annat konto. Du har flera konton Välj det konto som du vill logga in med. Microsoft Store & faktureringshjälp Hantera prenumerationer Returnerar & återbetalning Betalningsalternativ Orderhistorik Presentkort Installera Microsoft 365 Microsoft Store på Windows Utforska Microsoft Store-tjänster Vi är här för att hjälpa dig att göra mer med förstklassiga enheter, programvara, spel och resurser, från fri frakt och tillbaka till vårt prisskydd på 60 dagar. Ta en titt på vad Microsoft Store har att erbjuda: Köp och köp support | Konfiguration och utbildning av produkter | Small Business-support Köp och köp support Microsoft Store-tjänster är inte tillgängliga i alla regioner. Om du vill se vilka alternativ som är tillgängliga för dig väljer du land eller region i listrutan nedan och om det inte finns med i listan väljer du Andra regioner . Välj din region USA Australien Kanada (engelska) Kanada (franska) Storbritannien Andra regioner Varför handla i Microsoft Store Enkelt och bekvämt att handla Kostnadsfri 2-3 dagars frakt 60 dagars kostnadsfria returer 60 dagars prisskydd Flexibla betalningsalternativ Pengar för din begagnade enhet In- och återvinning Specialrabatter och erbjudanden För elever, föräldrar och lärare För militär personal Utökat enhetsskydd Microsoft Complete-skyddsplan Vi kan hjälpa dig att hitta det du behöver Supporthjälp för försäljning Answer desk för hjälpmedel Handla med en ASL-medarbetare Varför handla i Microsoft Store Enkelt och bekvämt att handla Fri frakt 60 dagars kostnadsfria returer 60 dagars prisskydd Pengar för din begagnade enhet In- och återvinning Specialrabatter och erbjudanden För elever, föräldrar och lärare Vi kan hjälpa dig att hitta det du behöver Supporthjälp för försäljning Answer desk för hjälpmedel Varför handla i Microsoft Store Enkelt och bekvämt att handla Fri frakt 60 dagars kostnadsfria returer 60 dagars prisskydd Pengar för din begagnade enhet In- och återvinning Specialrabatter och erbjudanden För elever, föräldrar och lärare Utökat enhetsskydd Microsoft Complete-skyddsplan Vi kan hjälpa dig att hitta det du behöver Om du har frågor innan du köper kan du chatta med en produktexpert eller boka ett shoppingmöte. Supporthjälp för försäljning Varför handla i Microsoft Store Enkelt och bekvämt att handla Fri frakt 60 dagars kostnadsfria returer 60 dagars prisskydd Pengar för din begagnade enhet In- och återvinning Specialrabatter och erbjudanden För elever, föräldrar och lärare Utökat enhetsskydd Microsoft Complete-skyddsplan Varför handla i Microsoft Store Enkelt och bekvämt att handla Fri frakt 60 dagars kostnadsfria returer 60 dagars prisskydd Pengar för din begagnade enhet In- och återvinning Specialrabatter och erbjudanden För elever, föräldrar och lärare Vi kan hjälpa dig att hitta det du behöver Supporthjälp för försäljning Answer desk för hjälpmedel Varför handla i Microsoft Store Vi kan hjälpa dig att hitta det du behöver Om du har frågor innan du köper kan du chatta med en produktexpert. Supporthjälp för försäljning Bläddra i Microsoft Store The Microsoft Store Konfiguration och utbildning av produkter Alla Microsoft Store-tjänster som anges här är inte tillgängliga i alla regioner. Om du vill se dina alternativ väljer du land eller region i listrutan nedan: Välj din region USA Australien Kanada (engelska) Kanada (franska) Storbritannien Andra regioner Hjälp- och utbildningsresurser Ta en titt på våra supportresurser för produkter som hjälper dig att hitta de svar du behöver. Surface-enheter | Xbox Microsoft 365 | Windows Hjälp- och utbildningsresurser Våra produktsupportresurser finns här för att hjälpa dig att hitta de svar du behöver. Surface-enheter | Xbox Microsoft 365 | Windows Hjälp- och utbildningsresurser Ta en titt på våra supportresurser för produkter som hjälper dig att hitta de svar du behöver. Surface-enheter | Xbox Microsoft 365 | Windows Hjälp- och utbildningsresurser Ta en titt på våra supportresurser för produkter som hjälper dig att hitta de svar du behöver. Surface-enheter | Xbox Microsoft 365 | Windows Hjälp- och utbildningsresurser Ta en titt på våra supportresurser för produkter som hjälper dig att hitta de svar du behöver. Surface-enheter | Xbox Microsoft 365 | Windows Hjälp- och utbildningsresurser Ta en titt på våra supportresurser för produkter som hjälper dig att hitta de svar du behöver. Surface-enheter | Xbox Microsoft 365 | Windows Small Business-support Om du vill se vilka supportalternativ för småföretag som är tillgängliga i din region väljer du land eller region i listrutan nedan: Välj din region USA Australien Kanada (engelska) Kanada (franska) Storbritannien Andra regioner Resurser för småföretag Få råd, kostnadsfri utbildning, produkter och verktyg som hjälper ditt företag att blomstra. Hjälp och utbildning för småföretag Resurscenter för småföretag Resurser för småföretag Få råd, kostnadsfri utbildning, produkter och verktyg som hjälper ditt företag att blomstra. Hjälp och utbildning för småföretag Resurscenter för småföretag Resurser för småföretag Få råd, kostnadsfri utbildning, produkter och verktyg som hjälper ditt företag att blomstra. Hjälp och utbildning för småföretag Resurscenter för småföretag Resurser för småföretag Vi kan hjälpa dig med allt från att bedöma dina affärsbehov till att hjälpa dig med konfiguration och felsökning. Få råd, kostnadsfri utbildning, produkter och verktyg som hjälper ditt företag att blomstra. Hjälp och utbildning för småföretag Resurscenter för småföretag Resurser för småföretag Få råd, kostnadsfri utbildning, produkter och verktyg som hjälper ditt företag att blomstra. Hjälp och utbildning för småföretag Resurscenter för småföretag Resurser för småföretag Få råd, kostnadsfri utbildning, produkter och verktyg som hjälper ditt företag att blomstra. Hjälp och utbildning för småföretag Nyheter Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot för organisationer Copilot för användning privat Microsoft 365 Utforska produkter från Microsoft Windows 11-appar Microsoft Store Kontoprofil Download Center Microsoft Store-support Returer Orderspårning Återvinning Kommersiella garantier Utbildning Microsoft Education Enheter för utbildning Microsoft Teams för utbildning Microsoft 365 Education Office Education Utbildning och utveckling för lärare Erbjudanden för elever och föräldrar Azure för studenter Företag Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Små företag Utvecklare och IT Microsoft Developer Microsoft Learn Stöd för AI-marknadsappar Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Företag Karriärmöjligheter Om Microsoft Företagsnyheter Sekretess på Microsoft Investerare Hållbarhet Svenska (Sverige) Ikon för inaktivering av sekretessval Dina sekretessval Ikon för inaktivering av sekretessval Dina sekretessval Sekretess för konsumenthälsa Kontakta Microsoft Integritet Hantera cookies Juridiskt meddelande Varumärken Om våra annonser EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:41 |
https://stateof.creativecommons.org/index.html#highlights | State of the Commons 2017 Highlights The Data The Tools The Community Financials English Català Indonesia 日本語 한국어 Español Dansk Svenska Euskara Highlights The Data The Tools The Community Financials English Català Indonesia 日本語 한국어 Español Dansk Svenska Euskara Facebook Twitter State of the Commons I use @creativecommons almost every day ... I don't want to live without you. - Julie Hiltz, NBCT @JulieHiltz Welcome Creative Commons is the leading organization supporting the global movement for sharing and collaboration. We create, maintain, and promote the Creative Commons licenses — free, international, easy-to-use copyright licenses that are the standard for enabling sharing and remix. We invigorate an international community of educators, activists, scientists, advocates, and creators to realize the benefits of the Commons. We build essential tools to make the Commons more discoverable, usable, and connected to communities everywhere. The past few years have been transformative for Creative Commons. In 2015, we set out with an ambitious new strategy to nurture a vibrant, usable Commons powered by collaboration and gratitude. Our ambition is fueled by our technology projects and an energetic and productive global community. Each of CC’s initiatives works in support of this goal, unleashing the potential of the Commons through the work of our committed global communities. In 2017, we hosted our largest Global Summit yet, organized by our community and supported by new sponsors and donors. With your guidance, we redesigned the Creative Commons Global Network in a massive, collaborative, international process, and we built new online infrastructure to support this unprecedented expansion of the movement for sharing. Our new engineering team shipped the CC Search beta and established new partnerships to expand our reach. We launched an exciting certification program, meeting demand for the course from librarians and educators around the world. We fought against the TPP and for copyright reform in Europe, and helped national governments adopt open education policies. With our help, UNESCO made significant progress this year towards open education policies and support for member states. We moved the needle on these issues while still maintaining and defending our core tools: CC licenses, which have been used well over a billion times by creators and rightsholders looking to expand the range of creativity and knowledge available to everyone. CC’s ambitious goals for the future will enable greater access and equality in education for everyone, accelerate innovation and discovery to cure disease, inspire delightful works of art and culture, and create deeper connections across cultures and communities. Our model is radically open, with community at the center. We believe sharing and collaboration can unlock the full potential for the Web, and more importantly, for all of the individuals who use it. It takes a group of driven, inspired, and talented humans to light up the Commons, and I feel privileged to work with them every day. You’ll see many of their stories in this year’s report — and that’s just a tiny percentage of the people who make this movement so powerful. We have the highest appreciation for those who make the choice to contribute to the Commons by freely sharing their work under CC licenses. With gratitude, Ryan Merkley CEO, Creative Commons 2017 Was a transformative year for Creative Commons We hosted our largest summit yet, organized by our community and supported by new sponsors and donors We redesigned the entire global network in a massive, collaborative, global process Our new development team shipped the CC search beta and struck new partnerships to expand our reach We launched a popular certification program, meeting unprecedented demand from librarians and educators around the world. We fought against the TPP We fought for copyright reform in Europe Contribute today to Creative Commons Support our projects in open education, open policy, and universal access to knowledge. Donate Now The Data 1.4 Billion Creative Commons Licensed Works 2017 100% 2016 82% 2015 76% 2014 60% 2010 27% 2006 10% Major Platforms sharing CC work 415.1 Million 49 million 46.7 million 40 million 36.9 million 28.7 million 6.6 million 3.1 million 2.7 million 2.3 million 1.2 million 740,896 556,126 200,000 114,969 Our Movement around the World 104 chapters across six regions North America: 2 Latin America: 16 Europe: 42 Africa: 7 Arab World: 6 Asia Pacific: 30 Search Countries that used CC Search the most in 2017: Sessions Queries Flag images by Ibrandify / Freepik Site Visitors Social Followers Most popular languages in 2017: English Spanish Portuguese German French Most popular shares on social media: Net Neutrality The Met Public Domain Open Access Did you know ? Europeana Collections showcases 42 openly licensed, designer, and sometimes quite crazy pairs of sunglasses. ‘The Kiss’, sunglasses by Oliver Goldsmith Eyewear, 1958. Courtesy Victoria and Albert Museum, CC BY The Tools Technology, Discovery, and Collaboration Tools A growing team with a broad scope and ambitious mandate is making the Commons more discoverable every day. Building a “front door to the Commons,” the revamped CC Search is the newest product in the CC Suite. In February 2017 we launched our CC Search product, lauded by press and users as the new “front door to the Commons.” We continued to add more images and features throughout 2017 and are continuing to grow the team. Under the leadership of our new Director of Product Engineering Paola Villarreal, the CC tech team deployed three new sites – State of the Commons, the 2018 Global Summit site, and the Certificates Program. In addition, we released the new membership site for our revived Global Network, launched our new Termination of Transfer Tool, and assisted on the refresh of our licenses, updating them to Python 3. Show More Show Less Creative Commons unveils a new photo search engine with filters, lists & social sharing: Finding free and legal images to accompany your web content has never been difficult, thanks to Creative Commons.” Techcrunch.com Open link Did you know ? In the weeks following the launch of the Met Museum’s CC0 open access initiative, image downloads from the collection increased by 260% Gift of Assunta Sommella Peluso, Ada Peluso, and Romano I. Peluso, in memory of Ignazio Peluso, 2003 CC0 Licenses and Legal Tools Our legal tools and licenses form the backbone of our work. This year, we marked several milestones to increase the robustness of our legal frameworks and tools for sharing on the web. In 2017, we welcomed seven new translations to the CC 4.0 license suite – Turkish, French, Italian, Swedish, Arabic, Croatian, and German, and three new translations of CC0 – Italian, Latvian, and Swedish. These languages are among the most spoken in the world, and the translation process is community-driven and draws on the expertise of our global network. As part of its stewardship responsibilities, CC closely tracked several disputes involving CC Licenses, intervening in one with a request to file an amicus brief to provide guidance on the proper interpretation of the licenses especially regarding the meaning of non-commercial. In each known instance, CC licenses were again enforced and interpreted properly, attesting to their robustness and clarity. In addition, we redesigned our deeds and framing of the license pages with an appealing modern refresh, submitted an application to be included in unicode (approved in 2018), and launched the landmark Termination of Transfer tool, which you can read more about below. In particular, the unicode approval is an exciting addition to our already robust portfolio – creators will easily be able to mark their CC-licensed works with icons in text and users will be able to provide attribution for CC-licensed works they use with icons. We also participated in forums to develop policies for preprint publication of scholarly works and data, and continue cross organizational support for products in development, supporting and protecting our trademarks and brands. Show More Show Less Project Profile RightsBack.org The Termination of Transfer (“ToT”) tool is a collaboration between Authors Alliance and Creative Commons that empowers authors to regain control of their work. The tool enables authors to learn about termination of transfer provisions, which allow authors to terminate licensing arrangements they have made with publishers that have prevented them from sharing openly or otherwise re-releasing their works. Anyone, including artists, photographers, scholars, and scientists, can use this new tool to discover more about eligibility and timing requirements for the right to take back rights previously assigned away. While this tool is currently U.S.-based only, Creative Commons plans to internationalize it for use worldwide. Show More Show Less Photo via Margorie Merel, CC BY Community Profile Margorie Merel A self-proclaimed “apostle” of the movement for the Commons in Panama, Margorie’s involvement with CC began as part of her academic research in Law and Political Science. As a steadfast advocate, Margorie has quickly become an integral part of the CC Network. This year, she appeared on Panamanian television to talk about the necessity of Creative Commons as well as presented her research to a number of local universities. For Margorie, “Teaching and sharing with teachers is the fundamental rock for me… I want to be part of a movement that believes in education, in the law; if we share we can build a better society with access to education. I like so much to teach, and CC provides the opportunity to get close to those people who can make a difference in my country.” Show More Show Less CC Tools and Platforms All over the world, commoners are celebrating, discussing, debating, and improving the Commons. With the kickoff of our new usability initiative, we’re ushering in a new phase of the Commons – one that makes it even easier to share. Beginning an exciting year with the launch of the Met Open Access initiative, usability at CC entered a new phase to home in on what makes sharing meaningful and how we can update our tools for a new age of the Web. Our major events in San Francisco, New York, DC, and Thailand explored these questions with CC platforms, makers, artists, technologists, and more. In April, we published the Kickstarter funded book Made with Creative Commons, exploring a range of “pro-social” uses of CC across business, nonprofits, the arts, and more. Show More Show Less With ‘Open Access,’ the Met Museum’s Digital Operation Has a Bona Fide Hit on Its Hands" – Artnet, August 10, 2017 Open link Photo by Scann, CC0 Community Impact Spotlight Scann + Open GLAM “CC has given me the space to help change the world I consider unfair and unjust. I want knowledge to be accessible for all and CC is a space where I feel I can achieve that.” - Evelin Heidel (Scann) An integral, long-term member of our global community, Evelin Heidel (Scann) is one of the leading advocates for global Open GLAM in Argentina and a strong voice for diversity and inclusion in our network. As a member of CC, Scann’s contributions to the Commons have been extensive and impactful: she’s helped build and install DIY Book Scanners at Argentine institutions to help them free their public domain books, translated articles, given workshops on digitization, organized the 2013 Global Summit in Buenos Aires, and helped to organize the Librebus Project in 2012. More recently, she was part of the Strategy Steering Committee and the Transition Committee for the CC Global Network. With a group of friends and colleagues, she works to maintain the public domain database of authors of Argentina. “One of the most important things about this community is that it has given me the chance to work with people and projects that I admire deeply, the kind of people and projects that I think have radically changed the way we see and have access to knowledge and culture,” says Scann. “Having the chance to work with those people and learn from them is one of the most astounding privileges I've had in my life, and for that I'm grateful.” Show More Show Less Ryan Merkley, Katherine Maher, and Mark Surman discuss the “Big Open” at MozFest 2017, London CC BY-SA 4.0 Project Spotlight The Big Open “As organizations, we have recently gone through processes to understand the future. What is interesting to me is that we have landed in a similar place, looking for the same thing.” – Katherine Maher, Executive Director, Wikimedia Foundation, 2017 As partners in the “Big Open,” we’re working together with other open organizations to usher in a new solidarity movement for the Commons. A new wave of momentum for our broad movements kicked off at Wikimania in August 2017. Together with our partners in the movement, notably Wikimedia Foundation and Mozilla, we’re coalescing around our shared values to mobilize people to action. As a big tent for political work, the Big Open is a vision of what radical global participation could look like. “As individuals, we wear many hats at once,” writes Alek Tarkowski of CC Poland. However, “across the world, our communities overlap… with many goals and projects. It is this movement that needs to be strengthened by our collective action, rather than just particular projects and organizations.” Building on a vision of community-centered open movements, the Big Open strives to work collaboratively to support our communities across projects and organizations. Show More Show Less It’s inspiring to see how creative people are when you make a collection like the Met’s accessible for them to use, share and remix without restriction.” - Loic Tallon, Met Museum Chief Digital Officer Houses with Red by Charles Demuth 1917 CC0 Certificates Mari Moreshead CC BY CC Certificates, a course built as an Open Educational Resource, kicked off at the end of 2017 with its first cohort of 50 librarians and educators working toward a more open world. In a two-year process culminating in 2017, CC built the curriculum for the CC Certificate, an online course targeted to librarians and educators to help them incorporate CC licenses and copyright education more effectively within their organizations and institutions. The team looks forward to expanding this program for other professions to meet the unprecedented demand for the course – the 50 person beta cohort was selected from more than 420 applicants. In addition to completing the course itself, the first group of participants gave week-by-week evaluations of the materials and assessments to help improve the course. Show More Show Less The Community Global Network In 2017, a revised community-driven strategy laid the groundwork for the CC Global Network to organize, collaborate, and share at a global scale. This year, we established four new organizing task forces for the global network: copyright reform, open education, GLAM, and community development. These platforms provide a new vision for the CC Network and a burgeoning era of awareness and advocacy for the Creative Commons. The process, organized over two years and including dozens of CC community members, created documentation to launch a revitalized membership program, providing volunteers the agency to self-organize at the local level with colleagues and peers working in the open. Show More Show Less No tool is better than the people who use it.” – Caroline Woolard, Artists in Conversation on Collaboration, Community, and the Commons Summit Creative Commons Global Summit 2017 Sebastiaan ter Burg CC BY 2.0 Sharing and the Commons: What’s next? The Global Summit, our annual gathering for the Commons, has become a sought-after event for Open Advocates around the world. More than 400 Commoners from over 60 countries gathered in Toronto for an amazing weekend of community, coalition building, and planning for the future of the CC Global Network. This year’s summit welcomed a record breaking 90 scholarship recipients – nearly a quarter of total participants. Highlights included over 100 sessions, 4 keynotes from internationally recognized activists, 5 tracks, and the incredible, 200 pound 3D replica of the Palmyra Tetrapylon presented by re:3D and the #NEWPALMYRA project. Show More Show Less Ken Bauer 2017/365/284 Uncommon Women CC BY-NC-SA 2.0 Project Spotlight UnCommon Women As part of the UnCommon Women initiative led by CC Canada Public Lead Kelsey Merkley, summit attendees were greeted with a coloring book of the faces of some of the most inspiring women from the Commons. In Kelsey’s words, “I started UnCommon Women because I wanted to celebrate and amplify the many strong, brilliant, and busy women of the Open Movement, across libraries, CC, Mozilla, academia, and Wikipedia.” UnCommon Women is building an uncommon community around the globe, facilitating conversations and connection around the need for women’s voices to be amplified in the Open Movement, tech, and beyond. Show More Show Less We're looking forward more than backward – taking this place that's a symbolic battleground for control over the Syrian cultural identity and its people, and freeing it, digitally." - Barry Threw, "How a 3D-printed piece of Palmyra landed in Toronto," CBC, May 02, 2017 Open link Creative Commons Global Summit 2017 by Sebastiaan ter Burg CC By 2.0 Policy We support progressive policy change by advocating for copyright reform in the public interest, promoting open access to scientific research and educational materials, protecting net neutrality, and calling for transparency and a rebalance of copyright rules negotiated via trade agreements. With more than 40 blog posts and whitepapers published this year alone, we’re a crucial voice in the conversation around the issues that matter most on the web – and getting stronger with the support of our Global Member Network. This year, we worked together to produce expert policy analyses and respond to public consultations on copyright matters. We contributed to relevant working groups and coalitions, including Communia, and we participated in a variety of key policy conferences and events, like Mozilla Festival, Rightscon, and WIPO. Show More Show Less Fundación Karisma, Colombia Community Impact Spotlight “Sharing is not a crime!” CC Supports Diego Gómez “Compartir no es delito!” “Sharing is not a crime!” The rallying cry was heard around the world, sounded by the civil society organization Fundación Karisma in support of Diego Gómez, a Colombian conservation biologist who was prosecuted for sharing a research paper online. Together with other organizations including EFF, Derechos Digitales, and SPARC, we provided crucial solidarity and support for this campaign, writing nine blog posts in English and Spanish, promoting on social media, and helping develop a crowdfunding campaign to help offset Diego’s massive legal costs. This year, Diego was acquitted on all charges, bringing a three year legal battle over the right to share to a close. Show More Show Less Foto de la charla "Ciberactivismo feminista" del Encuentro de Feministas Desorganizadas by Celeste Korol CC BY-SA 2.0 Community Profile Mariana Fossatti “I like to be a part of a community where I can act in a broad spectrum field that includes activists, artists, politicians, librarians, teachers, students, academics, and journalists. They have in common the fight for a more just world and an interest in social justice." Mariana has considered herself a free culture activist since she began using CC licenses for her own work ten years ago. In 2013, she joined with other activists and free culture organizations to found the CC Uruguay chapter, now one of the most active and prolific Creative Commons communities, and is a part of a collective of social organizations called Derecho a la Cultura. She is currently involved with a number of collaborative projects with CC UY, including Autores.uy for public domain works, the free music catalog Musica Libre, film and music festivals, and workshops about copyright and licensing. In the last few years, Mariana participated in the public campaign “Todos ganamos derechos” to support copyright reform in Uruguay. Mariana says, “Being part of a global movement allows activists to think and act locally, with tools that are useful for working with a large university or government, as well as with a local library or a collective of artists.” Show More Show Less Did you know ? PLOS counts 7,000 editorial board members and 70,000+ volunteer peer reviewers each year, all working under CC Licenses Open Education Our open education work focuses on advocacy and awareness-raising, open practices and policies, mentoring new leaders, co-leading the movement, and creating new OER production and adoption models. This year, Open Education celebrated a range of accomplishments all over the world, including: the 2nd World OER Congress and 2017 Ljubljana OER Action Plan; Cape Town Declaration +10; OER Policy Brief for the Commonwealth; Open Licensing Playbook for Government; national open education strategies in Romania, Morocco, South Africa, Kyrgyzstan, Slovenia, Bangladesh, Nigeria, Saudi Arabia and more; open licensing policies in the European Union, British Columbia and Alberta, and in US states and federal departments. Together with our community, we’re celebrating over 700 members in our new CC Open Education Platform, driving open education forward every day. Show More Show Less Community Profile Amanda Coolidge “I see CC individuals as leaders of change and I believe that this community will determine the direction our society is heading.” Amanda Coolidge is the Senior Manager for Open Education at BC Campus and works with all 25 public post secondary institutions in British Columbia to advocate for open education in Canada. A member of the CC Open Education platform, Amanda started the popular Twitter hashtag #500andcounting (now #700andcounting), a visibility campaign and call to action to champion the voices of the Open Education Movement, connecting open educators globally and help them spread the word. “I really love the passion of CC community members,” says Amanda. “The diversity of perspectives and the immense knowledge sharing is what draws me to this community. I love that the people involved in CC are involved because, like me, they believe that knowledge should be made accessible to all and that by sharing information we become better.” Show More Show Less Community Impact Spotlight CC Tanzania The Tanzanian CC Community has established a strong legal and advocacy framework to educate their community about the necessity of open access to knowledge. By conducting workshops, trainings, and meetings as well as building partnerships with aligned organizations, CC Tanzania has reached thousands and built the framework for continued partnership and cooperation within Tanzania and beyond. This year, CC Tanzania provided trainings for students, young librarians, and lawyers and promoted Open Access and Open Data in Africa through their accelerated community building work. Show More Show Less Community Building Since its launch in June of 2017, the Community Activities Fund has funded 27 projects across the globe and provided more than $17,000 for community projects. As facilitators of the Creative Commons movement, CC prioritizes the funding of community-led projects, including meetups, team building events, guidebooks, and salons. In addition, we’ve worked with a number of African community members to facilitate the growth of CC Communities across West Africa and in Zimbabwe, and to reinvigorate our work in Jordan and Venezuela. Show More Show Less Photo by joi Ito CC BY 2.0 Project Spotlight Bassel Khartabil Fellowship and Memorial Fund On August 1, 2017, we received the heartbreaking news that our friend Bassel (Safadi) Khartabil, detained since 2012, was executed by the Syrian government shortly after his 2015 disappearance. Khartabil was a Palestinian Syrian open internet activist, a free culture hero, and an important member of our community. In honor of his contributions to the Commons, Creative Commons and its partners launched both the Bassel Khartabil Memorial Fund and Free Culture Fellowship to continue his legacy. In less than a year, the memorial fund has raised $260,000 for free culture projects, programs, and grants to support individuals advancing collaboration, community building, and leadership development in the open communities of the Arab world. Show More Show Less Moh'd El Hafez Photography Community Impact Spotlight CC Jordan The revitalized CC Jordan community is a hub for Creative Commons activity in the Arab World. As advocates for a renewed Creative Commons presence in their local community, CC Jordan has been active with other organizations including Wikimedia Levant, TechWomen, Princess Sumaya University for Technology, and I-Dare organization. This year, CC Jordan restarted their country team with the help of our global Community Activities Fund and communications tools. Through meetings and events, they are building a network of members and volunteers, with one successful public gathering this year and more to come. Show More Show Less Did you know ? Wikimedia Commons has over 42 million files – all of them freely licensed. Credit: Basotxerri CC BY-SA 4.0 Financials Expenses Expense by program 2016 Audited Financials $ Education 85% $ Technology 49% $ International / Affiliates 41% $ Culture, Communications, Platform Support 41% $ Legal 24% $ Policy 12% $ Fundraising 45% $ Administration 40% Income Income by Category 2016 Audited Financials $ Foundations 86% $ Individual 10% $ Corporations 8% $ In-kind Donations 2% In 2016, Creative Commons received a transformative contribution of $10,000,000 from the The William and Flora Hewlett Foundation, which will be expended over a multi-year period to support the work of CC’s renewed organizational strategy. Thank you Creative Commons is grateful to our global community of foundations, sponsors, and individual donors who share our vision and make all our work possible. On behalf of the entire Creative Commons community – Board, staff, affiliates, and contributors from all over the world – thank you! Acknowledgements We gratefully acknowledge support from The William and Flora Hewlett Foundation as well as our lead community of donors, including Anonymous, Arcadia Fund, Argosy Foundation, Brin Wojcicki Foundation, Charles and Lynn Schusterman Family Foundation, CouponFollow, eCampus Ontario, Eric Saltzman and Victoria Munroe Charitable Fund, Ford Foundation, Google, Institute of Museum and Library Services, John S. and James L. Knight Foundation, Mozilla, Private Internet Access, Re:Create Coalition, Samuel H. Kress Foundation, Stewart J. Guss, Attorney at Law, and the Vadasz Family Foundation. We would like to acknowledge the following individuals and organizations for their contributions to this year’s State of the Commons report. Thank you! Growth Data Erin Simon & team, Google Eleanor Kenny, Europeana Liviu Iorgulescu, Jamendo Lila Bailey, Internet Archive Brian Carver, YouTube Danielle McKay, DeviantArt Cheyenne Hohman, Free Music Archive Ross Oldenburg, Free Music Archive Frank Polcino, Makerbot/Thingiverse Catherine Snow, Makerbot/Thingiverse Sylvia Ng, 500px Rommil Santiago, 500px Neil Quinn, Wikimedia Foundation Ed Erhart, Wikimedia Foundation Alex Feerst, Medium Simon Steinberger, Pixabay Matt Lee, Libre.fm Translations Coming soon. Attribution Attribution information is directly beneath or next to most images in the report. Any images that were not attributed directly in the report are listed below KPA_6840 Creative Commons Summit 2017 Photo by Kristina Alexanderson CC BY-SA 2.0 KPA_6833 Creative Commons Summit 2017 Photo by Kristina Alexanderson CC BY-SA 2.0 Jane Park at the Creative Commons Global Summit 2017 Photo by Sebastiaan ter Burg CC BY 2.0 KPA_6770 Creative Commons Summit 2017 Photo by Kristina Alexanderson CC BY-SA 2.0 terBurgDSCF0489 by Sebastiaan ter Burg CC BY 2.0 Megan with made with CC summit Photo by Jennie Rose Halperin CC BY 2.0 CC Summit 2011 Warsaw Photo by Kristina Alexanderson CC BY 2.0 Creative Commons Global Summit 2017 by Sebastiaan ter Burg CC BY 2.0 Creative Commons Global Summit 2017 by Sebastiaan ter Burg CC BY 2.0 Cable Green, Creative Commons Global Summit 2017 by Regina Gong CC BY 2.0 Creative Commons Global Summit 2017 by Sebastiaan ter Burg CC BY 2.0 Photo by Rebecca Lendl, CC BY Creative Commons Global Summit 2017 by Sebastiaan ter Burg CC BY 2.0 Creative Commons Global Summit 2017 by Sebastiaan ter Burg CC BY 2.0 Noun Project Icons Created by Nirbhay from the Noun Project Created by Eucalyp from the Noun Project Created by Prasad from the Noun Project Created by Icondesk from the Noun Project Created by useiconic.com from the Noun Project Data notes and sources Show Acknowledgements & Attribution Hide Acknowledgements & Attribution Contribute today to Creative Commons Together we can build a creative, free and open Commons. Donate Now We’d love to hear from you! info@creativecommons.org Frequently Asked Questions Except where otherwise stated, content on this site is licensed under a Creative Commons Attribution 4.0 international license . Website by Affinity Bridge Close Menu /* ----------------------------------------- */ /* Content Template: Quote - start */ /* ----------------------------------------- */ .quote { padding: 20px 0; } .quote__text { color: #ffffff; font-family: "Source Sans Pro", Sans-serif; font-size: 27px; font-weight: 700; line-height: 1.2em; margin-bottom: 0.8em; } .dark .quote__text { color: #222; } .big .quote__text { font-size: 59px; } .quote__attribution { color: #ffffff; font-family: "Source Sans Pro", Sans-serif; font-size: 18px; line-height: 1.2em; } .dark .quote__attribution { color: #333; } .big .quote__attribution { font-size: 20px; } .quote a { background: #EFBE00 url("/wp-content/uploads/2018/04/noun_45762_cc.svg") no-repeat 50% 50%; background-size: 20px; display: block; height: 40px; width: 40px; text-indent: 9999px; overflow: hidden; white-space: nowrap; position: absolute; right: 0px; bottom: -30px; } @media (max-width: 900px){ .big .quote__text { font-size: 5vw; line-height: 1em; } } @media (max-width: 768px){ .quote a { bottom: 0px; } .big .quote__text { font-size: 7vw; } } /* ----------------------------------------- */ /* Content Template: Quote - end */ /* ----------------------------------------- */ /* ----------------------------------------- */ /* Content Template: Did You Know? - start */ /* ----------------------------------------- */ .trivia { display: flex; justify-content: space-around; max-width: 1140px; margin: 0 auto; } .trivia h2 { align-self: center; color: #333333; font-family: "Source Sans Pro", Sans-serif; font-size: 3vw; font-weight: 700; text-transform: uppercase; line-height: 0.9em; padding: 0 2%; width: 17%; } [lang="id-ID"] .trivia h2 { font-size: 2.8vw; } .trivia h2 span { display: block; } .trivia__image { display: flex; padding: 0 2%; width: 18%; } .trivia__image img { align-self: center; max-height: 140px; flex-shrink: 0; } .trivia__text { align-self: center; width: 65%; padding: 0 2%; } .trivia__body { color: #333333; font-family: "Source Sans Pro", Sans-serif; font-size: 24px; line-height: 1.3em; margin-bottom: 1em; } .trivia__image_credit { color: #333333; font-family: "Source Sans Pro", Sans-serif; font-size: 14px; } @media (min-width: 1500px) { .trivia h2 { font-size: 3em; } } @media (max-width: 768px) { .trivia { flex-direction: column; justify-content: stretch; padding: 2em; text-align: center; } .trivia h2 { font-size: 2.4em; width: auto; } .trivia h2 span{ display: inline; } .trivia__image { align-self: center; padding-bottom: 1em; width: auto; } .trivia__text { width: auto; } } /* ----------------------------------------- */ /* Content Template: Did You Know? - end */ /* ----------------------------------------- */ /* ----------------------------------------- */ /* Content Template: SOTC Post – Large - start */ /* ----------------------------------------- */ .sotc-post { position: relative; } .sotc-post__image-credit { color: #fff; font-family: "Source Sans Pro", Sans-serif; font-size: 14px; } .sotc-post--large .sotc-post__image-credit { margin-top: -10px; margin-bottom: 10px; } .sotc-post--large .sotc-post__image-credit a { color: #fff; text-decoration: underline; } .sotc-post__intro-text { color: #222; font-family: "Source Sans Pro", Sans-serif; font-size: 44px; font-weight: 700; line-height: 1em; margin-bottom: 1em; } .sotc-post__expanded-text { background: #fff; clear: both; color: #333; display: none; font-family: "Source Sans Pro", Sans-serif; font-size: 21px; line-height: 1.5em; overflow: hidden; padding: 1.5em 1.5em 2.5em; } .sotc-post--large { margin-bottom: 60px; } .sotc-post--large img { margin-bottom: 2rem; } h2.sotc-post__headline { color: #fff; font-family: "Roboto Condensed", Sans-serif; font-size: 125px; font-weight: 600; hyphens: auto; line-height: 0.9em; text-transform: uppercase; } [lang="fr-FR"] h2.sotc-post__headline, [lang="sv-SE"] h2.sotc-post__headline, [lang="ko-KR"] h2.sotc-post__headline, [lang="es-ES"] h2.sotc-post__headline { line-height: 1em; } [lang="sv-SE"] h2.sotc-post__headline { font-size: 9vw; } .sotc-post--large .expanded-text__trigger { border-bottom: 1px solid #fff; } .sotc-post--large .expanded-text__trigger.open { border: none; margin-top: -41px; } .hide-show-button { background: #EFBE00; background-image: url("/wp-content/uploads/2018/04/arrow_down_blk.svg"); background-repeat: no-repeat; background-position: calc(100% - 0.5em) 50%; color: #222; cursor: pointer; display: inline-block; font-family: "Roboto Condensed", Sans-serif; font-size: 17px; font-weight: 600; padding: 0.3em 2em 0.3em 1em; text-transform: uppercase; } .hide-show-button.show-less { background-image: url("/wp-content/uploads/2018/04/arrow_up_blk.svg"); } .hide-show-button.show-less, .expanded-text__trigger.open .hide-show-button.show-more { display: none; } .expanded-text__trigger.open .hide-show-button.show-less { display: inline-block } @media (max-width:1024px) { h2.sotc-post__headline { font-size: 11vw; } .sotc-post__intro-text { font-size: 34px; margin-top: 1em; } } @media (max-width:768px) { .sotc-post__intro-text, .sotc-post--small .sotc-post__intro-text { font-size: 24px; line-height: 1.2em; } } /* ----------------------------------------- */ /* Content Template: SOTC Post – Large - end */ /* ----------------------------------------- */ /* ----------------------------------------- */ /* Content Template: SOTC Post – Small - start */ /* ----------------------------------------- */ .sotc-post--small { background: #fff; margin-bottom: 60px; overflow: auto; padding: 2rem; } .sotc-post--small img { float: left; margin: 0 2rem 5px 0; width: 32%; } .sotc-post__type { color: #333; font-family: "Source Sans Pro", Sans-serif; font-size: 18px; text-transform: uppercase; } h2.sotc-post__title { color: #19969C; cursor: pointer; font-family: "Source Sans Pro", Sans-serif; font-size: 40px; font-weight: 700; line-height: 1em; } .sotc-post--small .sotc-post__image-credit { clear: left; color: #333; float: left; font-family: "Source Sans Pro", Sans-serif; font-size: 14px; font-style: italic; width: 32%; line-height: 1em; } .sotc-post--small .sotc-post__intro-text { color: #222; font-family: "Source Sans Pro", Sans-serif; font-size: 24px; font-weight: 700; line-height: 1.3em; margin-bottom: 1em; margin-left: 34%; } .sotc-post--small .sotc-post__expanded-text { padding: 1.5em 0 2em; } .sotc-post--small .expanded-text__trigger { border: none; } .sotc-post--small .hide-show-button { bottom: 0; position: absolute; right: 0; } @media (max-width:1024px) { .sotc-post--small img { float: none; width: 100%; } .sotc-post--small .sotc-post__image-credit { float: none; margin-bottom: 1em; width: auto; } .sotc-post--small .sotc-post__intro-text { margin-left: 0; } .sotc-post--small .sotc-post__expanded-text { padding: 0 0 2em; } } @media (max-width:768px) { h2.sotc-post__title { font-size: 7vw; } } /* ----------------------------------------- */ /* Content Template: SOTC Post – Small - end */ /* ----------------------------------------- */ /* ----------------------------------------- */ /* Content Template: Credit listing - start */ /* ----------------------------------------- */ .credit { display: flex; color: #333; font-size: 1.1em; padding: 0 1em; } .credit-image { margin: 1em; width: 16%; } .credit-body { margin: 1em 0; line-height: 1.2em; } @media (max-width: 768px){ .credit { flex-direction: column; } .credit-image { margin: 0; width: auto; } } /* ----------------------------------------- */ /* Content Template: Credit listing - end */ /* ----------------------------------------- */ | 2026-01-13T09:29:41 |
https://support.microsoft.com/zh-cn/microsoft-store-and-billing | Microsoft Store 和计费帮助 跳转至主内容 Microsoft 支持 支持 支持 主页 Microsoft 365 Office 产品 Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows 更多信息 ... 设备 Surface 电脑配件 Xbox PC 游戏 HoloLens Surface Hub 硬件保修 帐户和计费 帐户 Microsoft Store 和计费 资源 新增功能 社区论坛 Microsoft 365 管理员 小型企业门户 开发人员 教育 上报支持欺诈 产品安全 更多 购买 Microsoft 365 所有 Microsoft Global Microsoft 365 Teams Windows Surface Xbox 折扣专区 企业购 支持 软件 软件 Windows 应用 AI OneDrive Outlook 从 Skype 转到 Teams OneNote Microsoft Teams PC 和设备 PC 和设备 购买 Xbox PC 和平板电脑 配件 娱乐 娱乐 Xbox 与游戏 PC 游戏 企业 企业 Microsoft 安全 Azure Dynamics 365 Microsoft 365 商业版 Microsoft 行业 Microsoft Power Platform 开发人员与 IT 开发人员与 IT Microsoft 开发人员 Microsoft Learn 支持 AI 商城应用 Microsoft 技术社区 Microsoft Marketplace Visual Studio Marketplace Rewards 其他 其他 免费下载与安全性 教育 查看站点地图 搜索 搜索帮助 无结果 取消 登录 使用 Microsoft 登录 登录或创建帐户。 你好， 使用其他帐户。 你有多个帐户 选择要登录的帐户。 Microsoft Store 和计费帮助 管理订阅 退货 & 退款 付款选项 订单历史记录 礼品卡 安装 Microsoft 365 Windows 上的 Microsoft 应用商店 探索 Microsoft Store 服务 从免费送货和退货到我们的 60 天价格保护，我们在这里帮助你使用一流的设备、软件、游戏和资源完成更多工作。 查看 Microsoft Store 必须提供的内容： 购物支持 | 产品设置和培训 | 小型企业支持 购物支持 Microsoft Microsoft Store 服务并非在所有区域都可用。 若要查看可用的选项，请从下面的下拉列表中选择你的国家或地区，如果未列出，请选择 其他区域 . 选择你的地区 United States Australia 加拿大（英语） 加拿大（法语） 英国 其他区域 为什么在Microsoft商店购物 轻松便捷的购物 2-3 天免费送货 60 天免费退货 60 天价格保护 灵活的付款选项 使用过的设备的现金 以旧换新和回收 特别折扣和优惠 面向学生、家长和教师 对于军事人员 扩展的设备保护 Microsoft完整的保护计划 我们可帮助你找到所需的内容 销售支持帮助 残障人士应答台 与 ASL 关联人员一起购物 为什么在Microsoft商店购物 轻松便捷的购物 免费送货 60 天免费退货 60 天价格保护 使用过的设备的现金 以旧换新和回收 特别折扣和优惠 面向学生、家长和教师 我们可帮助你找到所需的内容 销售支持帮助 残障人士应答台 为什么在Microsoft商店购物 轻松便捷的购物 免费送货 60 天免费退货 60 天价格保护 使用过的设备的现金 以旧换新和回收 特别折扣和优惠 面向学生、家长和教师 扩展的设备保护 Microsoft完整的保护计划 我们可帮助你找到所需的内容 如果在购买前有疑问，请与产品专家聊天或预约购物。 销售支持帮助 为什么在Microsoft商店购物 轻松便捷的购物 免费送货 60 天免费退货 60 天价格保护 使用过的设备的现金 以旧换新和回收 特别折扣和优惠 面向学生、家长和教师 扩展的设备保护 Microsoft完整的保护计划 为什么在Microsoft商店购物 轻松便捷的购物 免费送货 60 天免费退货 60 天价格保护 使用过的设备的现金 以旧换新和回收 特别折扣和优惠 面向学生、家长和教师 我们可帮助你找到所需的内容 销售支持帮助 残障人士应答台 为什么在Microsoft商店购物 我们可帮助你找到所需的内容 如果在购买前有疑问，请与产品专家聊天。 销售支持帮助 浏览Microsoft应用商店 Microsoft应用商店 产品设置和培训 并非所有此处列出的Microsoft应用商店服务都适用于所有区域。 若要查看选项，请从下面的下拉列表中选择你的国家或地区： 选择你的地区 United States Australia 加拿大（英语） 加拿大（法语） 英国 其他区域 帮助和学习资源 请查看我们的产品支持资源，以帮助你找到所需的答案。 Surface 设备 | Xbox Microsoft 365 | 窗户 帮助和学习资源 我们的产品支持资源可帮助你找到所需的答案。 Surface 设备 | Xbox Microsoft 365 | 窗户 帮助和学习资源 请查看我们的产品支持资源，以帮助你找到所需的答案。 Surface 设备 | Xbox Microsoft 365 | 窗户 帮助和学习资源 请查看我们的产品支持资源，以帮助你找到所需的答案。 Surface 设备 | Xbox Microsoft 365 | 窗户 帮助和学习资源 请查看我们的产品支持资源，以帮助你找到所需的答案。 Surface 设备 | Xbox Microsoft 365 | 窗户 帮助和学习资源 请查看我们的产品支持资源，以帮助你找到所需的答案。 Surface 设备 | Xbox Microsoft 365 | 窗户 小型企业支持 若要查看你所在区域可用的小型企业支持选项，请从下面的下拉列表中选择你的国家或地区： 选择你的地区 United States Australia 加拿大（英语） 加拿大（法语） 英国 其他区域 适用于小型企业的资源 获取建议、免费培训、产品和工具，以帮助企业蓬勃发展。 小型企业帮助和学习 小型企业资源汇 适用于小型企业的资源 获取建议、免费培训、产品和工具，以帮助企业蓬勃发展。 小型企业帮助和学习 小型企业资源汇 适用于小型企业的资源 获取建议、免费培训、产品和工具，以帮助企业蓬勃发展。 小型企业帮助和学习 小型企业资源中心 适用于小型企业的资源 从评估业务需求到协助设置和故障排除，我们在这里提供帮助。 获取建议、免费培训、产品和工具，以帮助企业蓬勃发展。 小型企业帮助和学习 小型企业资源中心 适用于小型企业的资源 获取建议、免费培训、产品和工具，以帮助企业蓬勃发展。 小型企业帮助和学习 小型企业资源汇 适用于小型企业的资源 获取建议、免费培训、产品和工具，以帮助企业蓬勃发展。 小型企业帮助和学习 新增内容 Surface Pro Surface Laptop 适用于组织的 Copilot Microsoft 365 探索 Microsoft 产品 Windows 11 应用程序 Microsoft Store 帐户个人资料 下载中心 订单跟踪 教育 Microsoft 教育版 教育设备 Microsoft Teams 教育版 Microsoft 365 教育版 Office 教育版 教育工作者培训和开发 面向学生和家长的优惠 面向学生的 Azure 企业 Microsoft 安全 Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 开发人员与 IT Microsoft 开发人员 Microsoft Learn 支持 AI 商城应用 Microsoft 技术社区 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 公司 招贤纳士 关于 Microsoft 公司新闻 Microsoft 隐私 投资人 可持续发展 中文(中国) 你的隐私选择选择退出图标 你的隐私选择 你的隐私选择选择退出图标 你的隐私选择 消费者健康隐私 与 Microsoft 联系 隐私 管理 Cookie 使用条款 商标 关于我们的广告 京ICP备09042378号-6 © Microsoft 2026 | 2026-01-13T09:29:41 |
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Fcoachhub--the-digital-coaching-platform&trk=products_details_guest_primary_call_to_action | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:41 |
https://stateof.creativecommons.org/index.html%3Flang=ja.html | State of the Commons 2017 ハイライト データ ツール コミュニティ 財務 日本語 English Català Indonesia 한국어 Español Dansk Svenska Euskara ハイライト データ ツール コミュニティ 財務 日本語 English Català Indonesia 한국어 Español Dansk Svenska Euskara Facebook Twitter State of the Commons 私は@creativecommonsを、ほとんど毎日使います ... あなたなしには生きられません - Julie Hiltz, NBCT @JulieHiltz ようこそ クリエイティブ・コモンズは、共有とコラボレーションのためのグローバルな活動組織です。 クリエイティブ・コモンズは、共有とリミックスのための無料の国際的で使いやすい著作権ライセンスを作成し、維持と普及活動を行なっています。 私たちは、教育関係者、社会活動家、科学者、支持団体、クリエイターからなる国際コミュニティを活性化させ、様々な「コモンズ」を支援しています。「コモンズ」の認知度と可用性を高め、あらゆる地域のコミュニティに結びつけるためのツールを提供しています。 ここ数年は、クリエイティブ・コモンズにとって変革の時期でした。2015年には、「コモンズ」のコラボレーションと活動力を高める野心的な新戦略を打ち出しました。CCのイニシアティブのそれぞれは、技術プロジェクトとグローバルコミュニティの活動を通じて「コモンズ」の潜在力を最大化します。 2017年には、新しいスポンサー達の支援を受けて最大規模のグローバルサミットを開催しました。私たちは大規模で国際的なクリエイティブ・コモンズのグローバル・ネットワークを再設計し、これを実現するために新しいオンライン・インフラを構築しました。新しい開発チームはCCサーチのベータ版をリリースし、作品へのリーチ数を高めました。 私たちは世界中の図書館員や教育関係者からの需要に応える認定プログラムを立ち上げました。私たちは、TPPや欧州の著作権の変更に反対し、各国政府のオープンな教育政策を支援しました。ユネスコは今年、オープン教育政策と加盟国への支援に向けて、私たちとのコラボレーションして成果をあげました。私たちは、CCのライセンスを保持しながら、これらの問題に取り組んできました。クリエイターと権利所有者が10億以上もの作品にCCライセンスを付与することで、誰もが利用可能な創造性と知識の利用範囲を拡大してきました。 私たちは、共有とコラボレーションがWebの潜在力を最大限に引き出すことができると信じています。 「コモンズ」を進化させるためには、強い意志と高い志をもつ才能ある人々が不可欠です。私たちは毎日、そのような人々と仕事をする恩恵を感じています。今年の報告書には、そのような話題が多く含まれていますが、これだけではありません。私たちは、CCライセンスに基づいてコモンズに貢献しているすべての人に最大の謝意を表します。 感謝をこめて Ryan Merkley CEO, Creative Commons 2017年はクリエイティブ・コモンズにとって変革の年でした 私たちのコミュニティと、新しいスポンサーと援助者の支援を受けて、最大規模のサミットを開催することができました。 私たちは、グローバルな組織全体を、より機動性と協調性を高めために再設計しました。 私たちの新しい開発チームは、CCサーチのベータ版をリリースし、作品へのリーチ数を高めました。 私たちは世界の図書館員や教育関係者からの要求に応え、認定プログラムを開始しました。 私たちはTPPに対して戦いました 私たちはヨーロッパで著作権の改革のために戦いました クリエイティブ・コモンズに貢献する 私たちのオープン教育、オープンポリシー、グローバルな知識共有のプロジェクトを支援してください。 寄付をお願いします データ 14億 クリエイティブ・コモンズ・ライセンス作品 2017 100% 2016 82% 2015 76% 2014 60% 2010 27% 2006 10% CC作品を共有する主要プラットフォーム 4億1510万 4,900万 4,670万 4,000万 3,690万 2,870万 660万 310万 270万 230万 120万 740,896 556,126 200,000 114,969 世界における 私たちの活動 6つの地域にまたがる104の支部 北米: 2 中南米: 16 ヨーロッパ: 42 アフリカ: 7 アラブ世界: 6 アジア太平洋: 30 サーチ 2017年にCCサーチを最も多く利用した国 セッション クエリ Ibrandify / Freepik による国旗イメージ サイト訪問者 ソーシャル・フォロワー 2017年に最も利用された言語 英語 スペイン語 ポルトガル語 ドイツ語 フランス語 最もシェアされたソーシャル・メディア 純中立性 メトロポリタン美術館パブリック・ドメイン オープン・アクセス ご存知でしたか？ ? ヨーロピアナ・コレクションズでは、オープンライセンスで提供されているデザイナーサングラス42点を展示しており、中にはなかなかクレイジーなものもあります。 ‘The Kiss’, sunglasses by Oliver Goldsmith Eyewear, 1958. Courtesy Victoria and Albert Museum, CC BY ツール テクノロジー、発見、そしてコラボレーションのためのツール 広い視野と強い使命感を持って成長を続けるコモンズのチームは、日々コモンズを見つけやすくしています。「コモンズの最初の扉」となった改良版CCサーチはCC Suiteの最新の製品です。 2017年2月、私たちはCCサーチを発表し、プレスやユーザーからは新しい「コモンズの最初の扉」だと、お褒めの言葉を頂きました。 2017年の間も、引き続きイメージや機能を追加し、チームを成長させてきました。製品エンジニアリングの新ディレクターPaola Villarreal（パオラ・ヴィラレアル）の指揮の下、CC技術チームは3つの新しいサイトを展開しました。「State of the Commons」、「2018年グローバル・サミット」、そして「認定プログラム」です。加えて、復活したグローバル・ネットワークのための新しいメンバーシップ・サイトの公開、新しくできたTermination of Transfer Toolの発表、そして私たちのライセンスを一新させるアシストをし、Python 3にアップデートしました。 更に表示 表示を戻す 「クリエイティブ・コモンズは、フィルター、リスト、ソーシャル・シェアリング機能を備えた新しい画像検索エンジンを公開しました。クリエイティブ・コモンズのおかげで、あなたのウェブコンテンツのためのフリーで合法的な画像を見つけるのはかつてないほど簡単になりました。」 Techcrunch.com ご存知でしたか？ ? メトロポリタン美術館がCC0オープン・アクセス・イニシアチブをローンチしたところ、数週間のうちに、画像のダウンロードは260％の増加を記録しました。 Gift of Assunta Sommella Peluso, Ada Peluso, and Romano I. Peluso, in memory of Ignazio Peluso, 2003 CC0 (Assunta Sommella Peluso、Ada Peluso、Romano I. Pelusoの寄贈。Ignazio Pelusoを記念して) ライセンスと法的ツール 私たちの法的ツールとライセンスは、私たちの活動の屋台骨です。今年は、ウェブ上でのシェアのための法的フレームワークとツールの堅牢さを強化するためのいくつかの画期的な達成をしました。 2017年、私たちは新たに7つの言語でCC 4.0ライセンス群の翻訳が提供されることを歓迎しました。トルコ語、フランス語、イタリア語、スウェーデン語、アラブ語、クロアチア語、ドイツ語です。また、CC 0も新たに3つの言語で翻訳が提供されました。イタリア語、ラトビア語、スウェーデン語です。これらの言語は世界で最も広く話されている言語の一部にあたり、翻訳のプロセスはコミュニティ主導で、私たちのグローバル・ネットワークの専門性に恩恵を受けました。CCは、ライセンス管理の責務の一環として、CCライセンスに関わるいくつかの係争に注視しました。その内の1件については、特に非営利の意味に関するライセンスの適切な解釈についてガイダンスを提供するためのアミカス・ブリーフを提出するリクエストと共に自ら介入しました。把握しているそれぞれの件で、CCライセンスは執行され、正しく解釈され、堅牢さと明瞭さを裏付けることになりました。 加えて、私たちは、コモンズ証とライセンスのページのフレームのデザインを改訂し時代にあったアピールを備えたものへとリフレッシュしました。ユニコードへの申請を提出し（2018年に承認）、記念すべき「解除移転ツール」（後述）のローンチも行いました。とりわけユニコードによる承認は、私たちの既に手堅いポートフォリオへの心躍る追加となりました。クリエイターは、テキスト内のアイコンを用いて、作品がCCライセンスされていることを簡単に示すことができ、利用者は、CCライセンスで提供されている作品を利用する際のクレジット表記をアイコンを使って提供することができるようになります。私たちは学術系の成果物とデータのプレプリント公開に関する政策策定のフォーラムに参加し、開発途中の製品への組織横断の支援を継続し、私たちの商標とブランドのサポートと保護を行いました。 更に表示 表示を戻す Photo via Margorie Merel, CC BY コミュニティ紹介 Margorie Merel パナマにおけるコモンズ運動の自称「使徒」であるマーゴリーのCCへの関与は法学と政治学の学術研究の一環として始まった。 確固たる主唱者として、マーゴリーはすぐにCCネットワークの不可欠な一部となりました。 今年、彼女はパナマのテレビでクリエイティブ・コモンズの必要性を語り、数多くの地元の大学において研究を発表しました。マーゴリーにとって、「教師との教えと分かちは、私の土台です...私は、教育、法律を信じるムーブメントの一部になりたいのです。もし、私たちが分かち合うなら、教育へのアクセスが確保されたより良い社会を築くことができます。私は教えるのが大好きで、CCは私の国に違いを生み出すことができる人々に近づく機会を提供してくれます。」 更に表示 表示を戻す プロジェクト紹介 RightsBack.org ターミネーション・オブ・トランスファー（Termination of Transfer (“ToT”)）は、作家を支援する団体Authors Allianceとクリエイティブ・コモンズのコラボレーションによってできた、作家が自身の作品の権利をもっとコントロールできるようにするためのツールです。 このツールによって、作家は、自由に共有したり再リリースすることの妨げとなっていた権利の移転に関する条項の終了について作家が学習し、それによって、この条項を終了させることができるようになります。芸術家、写真家、学者、科学者など誰しもがこの新しいツールを使って、過去に失った権利を復活させるための要素やタイミングを見つけることができます。 現在はまだ米国内での権利にしか適用できませんが、クリエイティブ・コモンズは今後、このツールが世界中で利用できるように国際化させる予定です。 更に表示 表示を戻す CCツールとプラットフォーム 世界中にいるクリエイティブ・コモンズの仲間たちは、その存在をたたえ、議論し、より良いものにしようとしています。新しく始まったユーザビリティ・イニシアチブによって、私たちは新しいフェーズに向かっています。これからは共有がもっともっと簡単になっていきます。 Met Open Accessイニシアチブの発動で始まったこのエキサイティングな年。CCのユーザビリティは新しいフェーズを迎えました。共有することの意義や、ウェブの新時代で使えるツールへとアップデートしていくことに力を注いでいこうとしています。 サンフランシスコ、ニューヨーク、ワシントンDC、タイなどで開催した大きなイベントでは、これらの課題について、CCプラットフォーム、メーカー、アーティスト、技術者など色々な人と考えました。4月にはKickstarterで集まった資金で「Made with Creative Commons」を出版し、ビジネス、非営利、芸術等でのCCの「プロソーシャル」な使い方について議論を展開しています。 更に表示 表示を戻す 「オープンアクセス」化により、メトロポリタン美術館のデジタル事業は善意と真実に包まれました。 – Artnet, 2017年8月10日 Photo by Scann, CC0 コミュニティ・インパクト・スポットライト Scann + Open GLAM 「CCは、私が不公正かつ不公平と考える世界を変える手助けをする空間を与えてくれました。 私はすべての人に知恵を提供したいと思うし、CCは私がそれを達成できると感じている場所です。」 - Evelin Heidel（Scann） 私たちのグローバルコミュニティに欠かせない長期的なメンバーであるEvelin Heidel（Scann）は、アルゼンチンにおけるグローバルOpen GLAMの主導者の1人であり、私たちのネットワークにおいて多様性と包摂性を強く訴えています。 CCの一員として、コモンズへのScannの貢献は広範かつインパクトがあります。パブリックドメインの書籍を無償化するアルゼンチンの施設にDIY Book Scannerをインストールすることを手伝ったり、記事を翻訳したり、デジタル化に関するワークショップを開催したり、ブエノスアイレスで行われた2013年のグローバルサミットを運営したり、2012年にLibrebusプロジェクトを組織するのに役立ちました。最近では、CCグローバルネットワークの戦略運営委員会と移行委員会の一員でした。友人や同僚と共に、彼女は彼女はアルゼンチンの作家のパブリックドメインのデータベースを維持管理するために働いています。「このコミュニティの最も重要なことの一つは、私が深く感心する人々やプロジェクト、私が見て知識にアクセスする方法を根本的に変えたと思う人々やプロジェクトと一緒に働く機会があることです」Scannはそう話します。「彼らと共に働き、彼らから学ぶ機会を持つことは、私の人生で最も驚くべき特権の1つであり、それに対して私は感謝しています。」 更に表示 表示を戻す Big Openについて議論するRyan Merkley、 Katherine Maher、Mark Surman（ロンドンでのMozFest 2017にて） CC BY-SA 4.0 プロジェクト・スポットライト Big Open 「いくつかの団体で、ここ最近、未来を理解するためのいくつかのプロセスを踏んできました。興味深いのは、みんなが似たようなところに着地したこと、同じものを見 据えたことです。」 -Katherine Maher（キャサリン・マー）（2017年。ウィキメディア財団エグゼクティブ・ディレクター） 私たちは「Big Open」のパートナーとして、コモンズのための新しい連帯運動を推し進めるためにも、他のオープン関連団体と一緒に活動しています。 この大きな運動に関しての新しい流れの契機となったのは2017年8月のWikimaniaでした。この運動に関わる他のパートナー、特にウィキメディア財団とMozillaと共に、人々が活動しやすいよう、共有する価値観を融合させています。政治的なところでは、Big Openは様々な意見を取り入れる場所となり、世界規模での急進的な参加がどういうものになりうるかというビジョンを示しています。CCポーランドのAlek Tarkowski（アレック・タルコウスキ）は、「各個人は、色々な役割を担っています。」と述べつつ「でも、世界を見てみると、コミュニティ同士で内容のかぶるところがあり、それぞれたくさんの目標やプロジェクトを抱えています。具体的なプロジェクトや団体が活発になるだけではなく、団結して行動することによってこの動きを強化させることが必要です。」と発言しています。コミュニティ中心のオープン・ムーブメントのビジョン以上に、Big Openは多数のコミュニティに関わる様々な各プロジェクトや各団体と共同でサポートしていたきたいと考えています。 更に表示 表示を戻す 創造的な人々がメトロポリタン美術館のコレクションを、無制限に利用し、共有し、リミックスしている状況に興奮しています。 - Loic Tallon, メトロポリタン美術館チーフ・デジタル・オフィサー チャールズ・デムース（Charles Demuth）の赤い家（1917年） （CC0） 認定コース Mari Moreshead CC BY CC認定コース（CC Certificates）は、オープン教育資源（OER）として作成されたコースで、2017年末に開始されました。最初の50名の図書館員や教育者のグループを迎え、よりオープンな世界へ向けて取り組んでいます。 図書館員や教育者が、所属する組織内でCCライセンスと著作権教育をより効果的に取り入れられるように、CCは2017年に至るまでの2年間の期間で、CC認定コースのカリキュラムをデザインしました。 このコースへのこれまでにない需要の高さに応えるべく、担当チームは、このプログラムを他の職種にも合うように拡張する意欲を持っています。50名のベータ・グループは420名以上の応募者の中から選ばれました。この最初の参加者のグループは、コースを修了することに加えて、毎週の教材やテスト問題等についての評価を提供し、コースの改善に力を貸しました。 更に表示 表示を戻す コミュニティ グローバル・ネットワーク 2017年には、コミュニティ主導戦略の見直しによって、コミュニティを世界規模でまとめ、協働し、共有するためのCCグローバルネットワークの基礎作りができました。 本年、私たちは、著作権改革、オープン教育、GLAM、コミュニティ開発という4つの新しい組織委員会を立ち上げました。 これらのプラットフォームはCCネットワークの新しいビジョンであり、クリエイティブ・コモンズにとっては認知度と支援が急速に高まる時代をつくるものとなります。 2年以上の歳月と何十人ものCCコミュニティのメンバーが関わって進めてきたこのプロセスは新しいメンバーシップ・プログラムを作るための文書を作りました。このプログラムでは、ボランティアで仲間たちと一緒にオープン関連のことをやりたいという人が、ローカルレベルで自分たちで活動できるよう、仲介者を紹介したりします。 更に表示 表示を戻す ツールそれ自体よりも、ツールを使いこなす人々の方がはるかに重要です。 – Caroline Woolard, コラボレーション、コミュニティ、コモンズにおける対話アーティスト サミット Creative Commons Global Summit 2017 Sebastiaan ter Burg CC BY 2.0 共有とコモンズ：次に始まるのは何？ 毎年コモンズが集結するイベント、グローバル・サミットは、世界中に散らばるオープン賛同者たちが開催を待ち遠しく思うものになりました。 60カ国以上から400名を超えるコモンズの仲間たちがトロントに集合しました。コミュニティや協調体制づくり、そしてCCグローバル・ネットワークの未来を考えるための素晴らしい週末を送ることとなりました。今回のサミットでは、これまでの記録更新となる90名（全参加者の1／4に近い数）ものスカラシップ獲得者が参加しました。ハイライトは100を超えるセッション、国際的に知られている活動家による4つの基調講演、5つの議題、そして200ポンド（約90キロ）のパルミラ遺跡の３Dレプリカ（re:3D and the #NEWPALMYRAプロジェクト提供）です。 更に表示 表示を戻す Ken Bauer 2017/365/284 Uncommon Women CC BY-NC-SA 2.0 プロジェクト・スポットライト UnCommon Women CCカナダの理事であるKelsey Markley（ケルシー・マークリー）率いる UnCommon Womenイニシアチブの一環として、コモンズにいる最も刺激的な女性たちの顔の「ぬり絵」でサミット参加者は迎えられました。 「私がUnCommon Womenを始めた理由は、図書館、CC、Mozilla、学会、ウィキペディア等でのオープン・ムーブメントで活躍する多くの強くて、輝いている、忙しい女性たちのことを称え、世に伝えたいと思ったから」とKelseyは言いました。 UnCommon Womenは、オープン・ムーブメント、テクノロジーなどで女性の声をもっと聞くべきという趣旨の交流やコネクション作りに役立つ珍しい（Uncommon）コミュニティづくりをしています。 更に表示 表示を戻す 私たちは過去よりも未来に期待しています - この場所は、シリアの文化的アイデンティティとその民衆を鼓舞し、それをデジタルで解放するための意義ある戦いの場です。 - Barry Threw, 「3D印刷されたパルミラ遺跡がいかにしてトロントに設置されたか」 CBC, 2017年5月2日 Sebastiaan ter Burg撮影 クリエイティブ・コモンズ・グローバル・サミット 2017 （CC By 2.0） 政策 私たちは、科学研究や教育素材を促進すること、ネットの中立性を守ること、そして著作権制度の透明性と再調整を要求することを通して、公共の利益のための著作権制度のリフォームを提言することによって、進歩的な政策変更をサポートしています。 今年だけで40以上のブログ記事と白書を公開しており、私たちはウェブ上で最も重要な問題に関する議論において重要な声であり、その声はグローバルメンバーネットワークのサポートによりますます強くなってきています。今年は、専門的な政策分析を作成し、著作権問題に関するパブリックコンサルテーションに対応するために協力しました。私たちは、Communiaを含む関連するワーキンググループや連携に貢献し、Mozilla Festival、Rightscon、そしてWIPOのような、さまざまな重要な政策会議やイベントに参加しました。 更に表示 表示を戻す Fundación Karisma, Colombia コミュニティ・インパクト・スポットライト “シェアすることは犯罪じゃない!” CC はディエゴ・ゴメズを支援 “Compartir no es delito!” "Sharing is not a crime!" （シェアすることは犯罪じゃない!）このスローガンは世界中で聞かれました。 市民セクターの組織であるカリスマ財団がディエゴ・ゴメズを支援するためにも声をあげました。彼はコロンビアの保全生物学者で、研究論文をオンラインでシェアしたことで起訴されました。 EFF、Derechos Digitales、SPARCといった組織と共に、私たちは決定的に重要な連帯を提供し、このキャンペーンを支援し、英語とスペイン語で9本のブログ記事を書き、ソーシャルメディアを通じて支援し、ディエゴの巨額の法的費用の支払いに力を添えるためのクラウドファンディング・キャンペーンの準備を手伝いました。今年、ディエゴは全ての嫌疑について無罪が言い渡され、シェアする権利をめぐる3年間の法的闘争が終結しました。 更に表示 表示を戻す Mariana Fossatti Photo by Celeste Korol CC BY-SA 2.0 コミュニティ紹介 Mariana Fossatti（マリアナ・フォサッティ） 「アクティビスト、アーティスト、政治家、図書館員、教師、学生、学者、ジャーナリストを含む幅広い領域で活動できるようなコミュニティの一部にいるのが私は好きです。彼らはより公正な(just) 世界への闘争と社会的正義への興味を共有しています。」マリアナは10年前にCCライセンスを使い始めてから自分をフリーカルチャーのアクティビストと考えています。 2013年、彼女は他のアクティビストやフリーカルチャー組織に加わりCCウルグアイ・チャプターを設立しました。CCウルグアイは現在ではクリエイティブ・コモンズの中でも最も活発で生産的なコミュニティのひとつで、Derecho a la Culturaという社会組織の集団の一部でもあります。彼女は現在CC UYの数々のコラボレーションプロジェクトに関わっており、 パブリックドメイン作品のためのAutores.uy、フリーなミュージックのカタログMusica Libre、映画祭や音楽祭、著作権とライセンシングに関するワークショップなどがあります。過去数年、マリアナは“Todos ganamos derechos”というキャンペーンに参加し、ウルグアイの著作権改正を支援しました。マリアナによれば「グローバルなムーブメントの一部でいることで、大きな大学や政府、地元の図書館やアーティスト団体とコラボレーションをするのに役に立つツールを使って、ローカルに考え・行動することができます」 更に表示 表示を戻す ご存知でしたか？ ? PLOS は7,000名の編集委員と、毎年70,000名を超えるボランティア査読者を擁しており、全ての記事がCCライセンスで提供されています。 オープン・エデュケーション オープン教育活動で焦点を当てているのはオープン教育を提唱しその意識を向上させること、実務や政策をオープンにしていくこと、新しく指導者となってくれる人を育てること、一緒に活動をリードしていくこと、そしてオープン・エデュケーション・リソースを作り、採用していくための新しいモデルを開発することです。 本年、オープン・エデュケーションは世界中で、以下に挙げるような様々な場面で業績を残しました。例えば、第2回OER世界会議の開催とそこで採択された2017年リュブリャナOERアクションプラン、ケープタウン宣言＋10、OER政策概要の作成、政府のためのOpen Licensing Playbook作成、ルーマニア・モロッコ・南アフリカ・キルギス・スロベニア・バングラデシュ・ナイジェリア・サウジアラビア他でのオープン教育に関する国家戦略、EU・ブリティッシュコロンビア州及びアルバータ州（カナダ）・アメリカ合衆国の州及び連邦機関でのオープンライセンスに関する政策の策定などです。また、新しくできたCCオープン・エデュケーション・プラットフォーム（CC Open Education Platform）に存在する700名を超えるメンバーと共に、さらにオープン教育を進めたいと考えています。 更に表示 表示を戻す コミュニティ・インパクト・スポットライト CCタンザニア タンザニアのCCコミュニティは、知識への自由なアクセスの必要性についてコミュニティを教育するための法とアドボカシーに関する強力なフレームワークを打ち立てました。 ワークショップ、トレーニング、会合を実施し、関係組織とのパートナーシップを構築し、CCタンザニアは何千もの人々にリーチし、タンザニア国内外での継続的な連携と強力のフレームワークを打ち立てました。今年はCCタンザニアは、コミュニティ形成の取り組みを加速させて、学生、若手の図書館員、および弁護士に対してトレーニングを提供し、アフリカにおけるオープンアクセスとオープンデータを後押ししました。 更に表示 表示を戻す コミュニティ紹介 Amanda Coolidge（アマンダ・クーリッジ） 「私はCCに関わる個人を変化のリーダーとみなし、このコミュニティが私たちの社会の方向性を決めると信じています。」 Amanda Coolidge（アマンダ・クーリッジ）は、BC Campusのオープン・エデュケーションのシニアマネージャであり、ブリティッシュ・コロンビア州にある25の公立高等教育機関と協力してカナダでのオープン教育を提唱しています。CCオープン・エデュケーションのプラットフォームの一員であるAmandaは世界中のオープンな教育者を結び付け、彼らがその声を広げることを助けるために、オープン・エデュケーション運動の声を支持するための人気のTwitterハッシュタグ＃500andcounting（今は＃700andcouting）と、オープン・エデュケーション運動の声明を支持するための視認性の高いキャンペーンと行動喚起を始めました。 「CCのコミュニティメンバーの情熱が本当に大好きです」とAmanda氏は言います。 「多様性の視点と莫大な知識共有が私をこのコミュニティに導きます。CCと関係のある人々と関わることが大好きです。なぜなら、私のように、知識はすべからくアクセスできるようになるべきであり、情報を共有することによって私たちがより良くなれると信じているからです。」 更に表示 表示を戻す コミュニティ・ビルディング Community Activities Fundは、2017年6月の開始以来、世界中の27のプロジェクトに資金を提供し、コミュニティ・プロジェクトに17,000ドル以上を拠出しました。 クリエイティブ・コモンズのムーブメントのファシリテーターとして、CCは、会議、チーム・ビルディング・イベント、ガイドブック、サロンなど、コミュニティ主導プロジェクトの資金調達を優先しています。 さらに、西アフリカとジンバブエのCCコミュニティの成長を促進し、ヨルダンとベネズエラでの活動を活性化するために、多くのアフリカのコミュニティメンバーと協力しました。 更に表示 表示を戻す Moh'd El Hafez Photography コミュニティ・インパクト・スポットライト CCヨルダン 再生されたCCヨルダンのコミュニティは、アラブ世界でのクリエイティブコモンズ活動の拠点です。 地域コミュニティにおける新しいクリエイティブ・コモンズの存在感を示す存在として、CCヨルダンは、Wikimedia Levant、TechWomen、Sumaya University for Technology、I-Dareを含む他の組織とともに活動しています。今年、CCヨルダンは、私たちのGlobal Community Activities Fundとコミュニケーションツールの助けを借りて、再スタートを切りました。今年、公式のミーティングを行うなど、ミーティングやイベントを通じて、メンバーとボランティアのネットワークを構築しています。 更に表示 表示を戻す Photo by joi Ito CC BY 2.0 プロジェクト・スポットライト Bassel Khartabilフェローシップと記念基金 2017年8月1日、私たちは、2012年以降拘留されていた友人バッセル（サファディ）ハルタビルが2015年の失踪直後にシリア政府によって処刑されていた、という悲しいニュースを受け取りました。 ハルタビルは、パレスチナのシリアのオープンインターネット活動家、フリーカルチャーのヒーロー、そして私たちのコミュニティの重要なメンバーでした。クリエイティブ・コモンズとそのパートナーは、彼のコモンズへの貢献を称えて、バッセル・ハルタビル記念基金とフリー・カルチャー・フェローシップを立ち上げ、彼のレガシーを継承します。1年足らずで記念基金は、アラブ世界のオープンコミュニティにおける協力、コミュニティ構築、指導力育成を促進する個人を支援するためのフリーカルチャーに関するプロジェクト、プログラム、助成金のために26万ドルを調達しました。 更に表示 表示を戻す ご存知でしたか？ ? ウィキメディア・コモンズは4200万点を超えるファイルを擁しており、全てフリーライセンスで提供されています。 クレジット: Basotxerri CC BY-SA 4.0 財務 費用 プログラム別費用 2016年監査済み財務 $ 教育 85% $ テクノロジー 49% $ 国際 / アフィリエイト 41% $ 文化、コミュニケーション、プラットフォーム・サポート 41% $ 法務 24% $ ポリシー 12% $ 資金調達 45% $ 管理 40% 収入 カテゴリー別収入 2016年監査済み財務 $ 財団 86% $ 個人 10% $ 企業 8% $ 現物寄付 2% 2016年に、クリエイティブ・コモンズは、ウィリアム・フローラ・ヒューレット財団から1,000万ドルの寄付を受けました。これは、CCの新たな組織戦略の活動を支援するために多年にわたり活用されます。 感謝します クリエイティブ・コモンズは、私たちのビジョンを共有し、すべての仕事を支援いただいた財団、スポンサー、個人援助団体のグローバル・コミュニティに謝意を表します。 世界のボードメンバー、スタッフ、関連グループ、貢献者のクリエイティブ・コモンズ・コミュニティ全体を代表して、ありがとう！ 謝辞 私たちは、ウィリアム・フローラ・ヒューレット財団、匿名者、アルカディア・ファンド、アーゴディア基金、ブリン・ウォジキチ財団、チャールズ・アンド・リン・シュスターマン家族財団、クーポン・フォロー、eCampusオンタリオ、エリック・サルトマン、ビクトリア・モンロー慈善基金、フォード財団、Google、博物館と図書館サービスの研究所、ジョンS. & ジェームズL.ナイト財団、Mozilla、プライベートインターネットアクセス、Re:Create Coalition、サミュエルH.クレス財団、スチュワートJ.グース、弁護士、およびVadasz家族財団からの寄付を受けました。 今年のコモンズ報告書に貢献した以下の個人および団体に感謝したいと思います。ありがとうございました！ Erin Simonとそのチーム, Google Eleanor Kenny, Europeana Liviu Iorgulescu, Jamendo Lila Bailey, Internet Archive Brian Carver, YouTube Danielle McKay, DeviantArt Cheyenne Hohman, Free Music Archive Ross Oldenburg, Free Music Archive Frank Polcino, Makerbot/Thingiverse Catherine Snow, Makerbot/Thingiverse Sylvia Ng, 500px Rommil Santiago, 500px Neil Quinn, Wikimedia Foundation Ed Erhart, Wikimedia Foundation Alex Feerst, Medium Simon Steinberger, Pixabay Matt Lee, Libre.fm 翻訳 まもなく公開 アトリビューション アトリビューション情報は、レポートのほとんどの画像のすぐ下、または横に表示されています。レポートに直接表示されなかった画像は以下のとおりです Cable Green, Creative Commons Global Summit 2017 by Regina Gong CC BY 2.0 Sebastiaan ter Burg撮影 Creative Commons Global Summit 2017 （CC BY 2.0） CC Summit 2011 Warsaw by Kristina Alexanderson CC BY 2.0 Sebastiaan ter Burg撮影 クリエイティブ・コモンズ・グローバル・サミット 2017 （CC BY 2.0） Sebastiaan ter Burg撮影 クリエイティブ・コモンズ・グローバル・サミット 2017 （CC BY 2.0） Sebastiaan ter Burg撮影 クリエイティブ・コモンズ・グローバル・サミット 2017 （CC BY 2.0） Sebastiaan ter Burg撮影 クリエイティブ・コモンズ・グローバル・サミット 2017 （CC BY 2.0） Rebecca Lendl撮影 （CC BY） Jennie Rose Halperin撮影 CCサミットのMegan （CC BY 2.0） by Sebastiaan ter Burg撮影 terBurgDSCF0489 （CC BY 2.0） Kristina Alexanderson撮影 KPA_6770 Creative Commons Summit 2017 （CC BY-SA 2.0） Sebastiaan ter Burg 撮影 Jane Park at the Creative Commons Global Summit 2017 （CC BY 2.0） ristina Alexanderson撮影 KPA_6833 Creative Commons Summit 2017 （CC BY-SA 2.0） Kristina Alexanderson撮影 KPA_6840 Creative Commons Summit 2017 （CC BY-SA 2.0） Noun Project アイコン Noun ProjectのNirbhay による制作 Noun Projectの Eucalyp により制作 Noun Projectの Prasad により制作 Noun Projectの Icondesk により制作 Noun Projectの useiconic.com により制作 情報源 承認と所属の表示 承認と所属の非表示 クリエイティブ・コモンズに貢献する 一緒に、創造的で自由でオープンな「コモンズ」を築きましょう。 寄付をお願いします あなたのご意見をお待ちしています！ info@creativecommons.org FAQ 特に明記されない限り、このサイトのコンテンツは CC 4.0アトリビューション国際ライセンス . Affinity Bridge ウェブサイトの元にライセンスされています Close Menu /* ----------------------------------------- */ /* Content Template: Quote - 開始 */ /* ----------------------------------------- */ .quote { padding: 20px 0; } .quote__text { color: #ffffff; font-family: "Source Sans Pro", Sans-serif; font-size: 27px; font-weight: 700; line-height: 1.2em; margin-bottom: 0.8em; } .dark .quote__text { color: #222; } .big .quote__text { font-size: 59px; } .quote__attribution { color: #ffffff; font-family: "Source Sans Pro", Sans-serif; font-size: 18px; line-height: 1.2em; } .dark .quote__attribution { color: #333; } .big .quote__attribution { font-size: 20px; } .quote a { background: #EFBE00 url("/wp-content/uploads/2018/04/noun_45762_cc.svg") no-repeat 50% 50%; background-size: 20px; display: block; height: 40px; width: 40px; text-indent: 9999px; overflow: hidden; white-space: nowrap; position: absolute; right: 0px; bottom: -30px; } @media (max-width: 900px){ .big .quote__text { font-size: 5vw; line-height: 1em; } } @media (max-width: 768px){ .quote a { bottom: 0px; } .big .quote__text { font-size: 7vw; } } /* ----------------------------------------- */ /* Content Template: Quote - 終了 */ /* ----------------------------------------- */ /* ----------------------------------------- */ /* Content Template: Did You Know? - 開始 */ /* ----------------------------------------- */ .trivia { display: flex; justify-content: space-around; max-width: 1140px; margin: 0 auto; } .trivia h2 { align-self: center; color: #333333; font-family: "Source Sans Pro", Sans-serif; font-size: 3vw; font-weight: 700; text-transform: uppercase; line-height: 0.9em; padding: 0 2%; width: 17%; } [lang="id-ID"] .trivia h2 { font-size: 2.8vw; } .trivia h2 span { display: block; } .trivia__image { display: flex; padding: 0 2%; width: 18%; } .trivia__image img { align-self: center; max-height: 140px; flex-shrink: 0; } .trivia__text { align-self: center; width: 65%; padding: 0 2%; } .trivia__body { color: #333333; font-family: "Source Sans Pro", Sans-serif; font-size: 24px; line-height: 1.3em; margin-bottom: 1em; } .trivia__image_credit { color: #333333; font-family: "Source Sans Pro", Sans-serif; font-size: 14px; } @media (min-width: 1500px) { .trivia h2 { font-size: 3em; } } @media (max-width: 768px) { .trivia { flex-direction: column; justify-content: stretch; padding: 2em; text-align: center; } .trivia h2 { font-size: 2.4em; width: auto; } .trivia h2 span{ display: inline; } .trivia__image { align-self: center; padding-bottom: 1em; width: auto; } .trivia__text { width: auto; } } /* ----------------------------------------- */ /* Content Template: Did You Know? - 終了 */ /* ----------------------------------------- */ /* ----------------------------------------- */ /* Content Template: SOTC Post – Large - 開始 */ /* ----------------------------------------- */ .sotc-post { position: relative; } .sotc-post__image-credit { color: #fff; font-family: "Source Sans Pro", Sans-serif; font-size: 14px; } .sotc-post--large .sotc-post__image-credit { margin-top: -10px; margin-bottom: 10px; } .sotc-post--large .sotc-post__image-credit a { color: #fff; text-decoration: underline; } .sotc-post__intro-text { color: #222; font-family: "Source Sans Pro", Sans-serif; font-size: 44px; font-weight: 700; line-height: 1em; margin-bottom: 1em; } .sotc-post__expanded-text { background: #fff; clear: both; color: #333; display: none; font-family: "Source Sans Pro", Sans-serif; font-size: 21px; line-height: 1.5em; overflow: hidden; padding: 1.5em 1.5em 2.5em; } .sotc-post--large { margin-bottom: 60px; } .sotc-post--large img { margin-bottom: 2rem; } h2.sotc-post__headline { color: #fff; font-family: "Roboto Condensed", Sans-serif; font-size: 125px; font-weight: 600; hyphens: auto; line-height: 0.9em; text-transform: uppercase; } [lang="fr-FR"] h2.sotc-post__headline, [lang="sv-SE"] h2.sotc-post__headline, [lang="ko-KR"] h2.sotc-post__headline, [lang="es-ES"] h2.sotc-post__headline { line-height: 1em; } [lang="sv-SE"] h2.sotc-post__headline { font-size: 9vw; } .sotc-post--large .expanded-text__trigger { border-bottom: 1px solid #fff; } .sotc-post--large .expanded-text__trigger.open { border: none; margin-top: -41px; } .hide-show-button { background: #EFBE00; background-image: url("/wp-content/uploads/2018/04/arrow_down_blk.svg"); background-repeat: no-repeat; background-position: calc(100% - 0.5em) 50%; color: #222; cursor: pointer; display: inline-block; font-family: "Roboto Condensed", Sans-serif; font-size: 17px; font-weight: 600; padding: 0.3em 2em 0.3em 1em; text-transform: uppercase; } .hide-show-button.show-less { background-image: url("/wp-content/uploads/2018/04/arrow_up_blk.svg"); } .hide-show-button.show-less, .expanded-text__trigger.open .hide-show-button.show-more { display: none; } .expanded-text__trigger.open .hide-show-button.show-less { display: inline-block } @media (max-width:1024px) { h2.sotc-post__headline { font-size: 11vw; } .sotc-post__intro-text { font-size: 34px; margin-top: 1em; } } @media (max-width:768px) { .sotc-post__intro-text, .sotc-post--small .sotc-post__intro-text { font-size: 24px; line-height: 1.2em; } } /* ----------------------------------------- */ /* Content Template: SOTC Post – Large - 終了 */ /* ----------------------------------------- */ /* ----------------------------------------- */ /* Content Template: SOTC Post – Small - 開始 */ /* ----------------------------------------- */ .sotc-post--small { background: #fff; margin-bottom: 60px; overflow: auto; padding: 2rem; } .sotc-post--small img { float: left; margin: 0 2rem 5px 0; width: 32%; } .sotc-post__type { color: #333; font-family: "Source Sans Pro", Sans-serif; font-size: 18px; text-transform: uppercase; } h2.sotc-post__title { color: #19969C; cursor: pointer; font-family: "Source Sans Pro", Sans-serif; font-size: 40px; font-weight: 700; line-height: 1em; } .sotc-post--small .sotc-post__image-credit { clear: left; color: #333; float: left; font-family: "Source Sans Pro", Sans-serif; font-size: 14px; font-style: italic; width: 32%; line-height: 1em; } .sotc-post--small .sotc-post__intro-text { color: #222; font-family: "Source Sans Pro", Sans-serif; font-size: 24px; font-weight: 700; line-height: 1.3em; margin-bottom: 1em; margin-left: 34%; } .sotc-post--small .sotc-post__expanded-text { padding: 1.5em 0 2em; } .sotc-post--small .expanded-text__trigger { border: none; } .sotc-post--small .hide-show-button { bottom: 0; position: absolute; right: 0; } @media (max-width:1024px) { .sotc-post--small img { float: none; width: 100%; } .sotc-post--small .sotc-post__image-credit { float: none; margin-bottom: 1em; width: auto; } .sotc-post--small .sotc-post__intro-text { margin-left: 0; } .sotc-post--small .sotc-post__expanded-text { padding: 0 0 2em; } } @media (max-width:768px) { h2.sotc-post__title { font-size: 7vw; } } /* ----------------------------------------- */ /* Content Template: SOTC Post – Small - 終了 */ /* ----------------------------------------- */ /* ----------------------------------------- */ /* Content Template: Credit listing - 開始 */ /* ----------------------------------------- */ .credit { display: flex; color: #333; font-size: 1.1em; padding: 0 1em; } .credit-image { margin: 1em; width: 16%; } .credit-body { margin: 1em 0; line-height: 1.2em; } @media (max-width: 768px){ .credit { flex-direction: column; } .credit-image { margin: 0; width: auto; } } /* ----------------------------------------- */ /* Content Template: Credit listing - 終了 */ /* ----------------------------------------- */ | 2026-01-13T09:29:41 |
https://support.microsoft.com/pl-pl/microsoft-store-and-billing | Microsoft Store i pomoc dotycząca rozliczeń Przejdź do głównej zawartości Microsoft Pomoc techniczna Pomoc techniczna Pomoc techniczna Strona główna Microsoft 365 Office Produkty Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows więcej... Urządzenia Surface Akcesoria komputerowe Xbox Gry komputerowe HoloLens Surface Hub Gwarancje sprzętowe Konto i rozliczenia klient Sklep Microsoft Store & rozliczenia Zasoby Co nowego Fora społeczności Administratorzy platformy Microsoft 365 Portal dla małych firm Deweloper Edukacja Zgłoś oszustwo związane z pomocą techniczną Bezpieczeństwo produktu Więcej Kup platformę Microsoft 365 Wszystkie produkty Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Promocje i zniżki Pomoc techniczna Oprogramowanie Oprogramowanie Aplikacje systemu Windows AI OneDrive Outlook Przejście ze Skype do Teams OneNote Microsoft Teams Komputery i urządzenia Komputery i urządzenia Kup Xbox Akcesoria Rozrywka Rozrywka Xbox Game Pass Ultimate Xbox i gry Gry PC Sklep dla firm Sklep dla firm Rozwiązania zabezpieczające firmy Microsoft Azure Dynamics 365 Microsoft 365 dla firm Rozwiązania Microsoft dla przedsiębiorstw Microsoft Power Platform Windows 365 Dla programistów i specjalistów IT Dla programistów i specjalistów IT Deweloper Microsoft Microsoft Learn Pomoc techniczna do aplikacji z platformy handlowej opartych na AI Społeczność Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards Inny Inny Bezpłatne pliki do pobrania i zabezpieczenia Edukacja Bony upominkowe Licencjonowanie Wyświetl mapę witryny Wyszukaj Wyszukaj, aby uzyskać pomoc Brak wyników Anuluj Zaloguj się Zaloguj się przy użyciu konta Microsoft Zaloguj się lub utwórz konto. Witaj, Wybierz inne konto. Masz wiele kont Wybierz konto, za pomocą którego chcesz się zalogować. Microsoft Store i pomoc dotycząca rozliczeń Zarządzanie subskrypcjami Zwraca & zwroty kosztów Opcje płatności Historia zamówień Upominkowe Instalowanie platformy Microsoft 365 Microsoft Store w systemie Windows Poznaj usługi Microsoft Store Od bezpłatnej wysyłki i zwrotów po 60-dniową ochronę cen — pomożemy Ci zrobić więcej dzięki najlepszym w klasie urządzeniom, oprogramowaniu, gram i zasobom. Sprawdź, co oferuje sklep Microsoft Store: Pomoc techniczna dotycząca zakupów i zakupów | Konfiguracja produktu i szkolenia | Pomoc techniczna dla małych firm Pomoc techniczna dotycząca zakupów i zakupów Usługi sklepu Microsoft Store nie są dostępne we wszystkich regionach. Aby sprawdzić, jakie opcje są dla Ciebie dostępne, wybierz swój kraj lub region z poniższej listy rozwijanej, a jeśli nie ma jej na liście, wybierz pozycję Inne regiony . Wybierz swój region Stany Zjednoczone Australia Kanada (angielski) Kanada (francuski) Zjednoczone Królestwo Inne regiony Dlaczego warto kupować w Sklepie Microsoft Łatwe i wygodne zakupy Bezpłatna wysyłka 2–3 dni Bezpłatne zwroty 60-dniowe 60-dniowa ochrona ceny Elastyczne opcje płatności Gotówka za używane urządzenie Handel i recykling Specjalne rabaty i oferty Dla uczniów, rodziców i nauczycieli Dla personelu wojskowego Rozszerzona ochrona urządzenia Plan ochrony Microsoft Complete Pomożemy Ci znaleźć to, czego potrzebujesz Wsparcie sprzedaży Dział answer desk dla osób niepełnosprawnych Kup u współpracownika ASL Dlaczego warto kupować w Sklepie Microsoft Łatwe i wygodne zakupy Bezpłatna wysyłka Bezpłatne zwroty 60-dniowe 60-dniowa ochrona ceny Gotówka za używane urządzenie Handel i recykling Specjalne rabaty i oferty Dla uczniów, rodziców i nauczycieli Pomożemy Ci znaleźć to, czego potrzebujesz Wsparcie sprzedaży Dział answer desk dla osób niepełnosprawnych Dlaczego warto kupować w Sklepie Microsoft Łatwe i wygodne zakupy Bezpłatna wysyłka Bezpłatne zwroty 60-dniowe 60-dniowa ochrona ceny Gotówka za używane urządzenie Handel i recykling Specjalne rabaty i oferty Dla uczniów, rodziców i nauczycieli Rozszerzona ochrona urządzenia Plan ochrony Microsoft Complete Pomożemy Ci znaleźć to, czego potrzebujesz Jeśli masz pytania przed zakupem, porozmawiaj z ekspertem ds. produktów lub zarezerwuj spotkanie na zakupy. Wsparcie sprzedaży Dlaczego warto kupować w Sklepie Microsoft Łatwe i wygodne zakupy Bezpłatna wysyłka Bezpłatne zwroty 60-dniowe 60-dniowa ochrona ceny Gotówka za używane urządzenie Handel i recykling Specjalne rabaty i oferty Dla uczniów, rodziców i nauczycieli Rozszerzona ochrona urządzenia Plan ochrony Microsoft Complete Dlaczego warto kupować w Sklepie Microsoft Łatwe i wygodne zakupy Bezpłatna wysyłka Bezpłatne zwroty 60-dniowe 60-dniowa ochrona ceny Gotówka za używane urządzenie Handel i recykling Specjalne rabaty i oferty Dla uczniów, rodziców i nauczycieli Pomożemy Ci znaleźć to, czego potrzebujesz Wsparcie sprzedaży Dział answer desk dla osób niepełnosprawnych Dlaczego warto kupować w Sklepie Microsoft Pomożemy Ci znaleźć to, czego potrzebujesz Jeśli masz pytania przed zakupem, porozmawiaj z ekspertem ds. produktów. Wsparcie sprzedaży Przeglądanie Sklepu Microsoft Sklep Microsoft Konfiguracja produktu i szkolenia Nie wszystkie wymienione tutaj usługi Sklepu Microsoft są dostępne we wszystkich regionach. Aby wyświetlić opcje, wybierz swój kraj lub region z poniższej listy rozwijanej: Wybierz swój region Stany Zjednoczone Australia Kanada (angielski) Kanada (francuski) Zjednoczone Królestwo Inne regiony Pomoc i materiały szkoleniowe Zapoznaj się z naszymi zasobami pomocy technicznej dla produktów, które pomogą Ci znaleźć potrzebne odpowiedzi. Urządzenia Surface | Xbox Microsoft 365 | Windows Pomoc i materiały szkoleniowe Nasze zasoby pomocy technicznej dotyczące produktów są tutaj, aby pomóc Ci znaleźć potrzebne odpowiedzi. Urządzenia Surface | Xbox Microsoft 365 | Windows Pomoc i materiały szkoleniowe Zapoznaj się z naszymi zasobami pomocy technicznej dla produktów, które pomogą Ci znaleźć potrzebne odpowiedzi. Urządzenia Surface | Xbox Microsoft 365 | Windows Pomoc i materiały szkoleniowe Zapoznaj się z naszymi zasobami pomocy technicznej dla produktów, które pomogą Ci znaleźć potrzebne odpowiedzi. Urządzenia Surface | Xbox Microsoft 365 | Windows Pomoc i materiały szkoleniowe Zapoznaj się z naszymi zasobami pomocy technicznej dla produktów, które pomogą Ci znaleźć potrzebne odpowiedzi. Urządzenia Surface | Xbox Microsoft 365 | Windows Pomoc i materiały szkoleniowe Zapoznaj się z naszymi zasobami pomocy technicznej dla produktów, które pomogą Ci znaleźć potrzebne odpowiedzi. Urządzenia Surface | Xbox Microsoft 365 | Windows Pomoc techniczna dla małych firm Aby sprawdzić, jakie opcje pomocy technicznej dla małych firm są dostępne w Twoim regionie, wybierz swój kraj lub region z poniższej listy rozwijanej: Wybierz swój region Stany Zjednoczone Australia Kanada (angielski) Kanada (francuski) Zjednoczone Królestwo Inne regiony Zasoby dla twojej małej firmy Uzyskaj porady, bezpłatne szkolenia, produkty i narzędzia, które pomogą Twojej firmie rozwijać się. Pomoc i nauka w małych firmach Centrum zasobów małych firm Zasoby dla twojej małej firmy Uzyskaj porady, bezpłatne szkolenia, produkty i narzędzia, które pomogą Twojej firmie rozwijać się. Pomoc i nauka w małych firmach Centrum zasobów małych firm Zasoby dla twojej małej firmy Uzyskaj porady, bezpłatne szkolenia, produkty i narzędzia, które pomogą Twojej firmie rozwijać się. Pomoc i nauka w małych firmach Centrum zasobów małych firm Zasoby dla twojej małej firmy Od oceniania potrzeb biznesowych po pomoc w konfiguracji i rozwiązywaniu problemów — jesteśmy tu, aby Ci pomóc. Uzyskaj porady, bezpłatne szkolenia, produkty i narzędzia, które pomogą Twojej firmie rozwijać się. Pomoc i nauka dla małych firm Centrum zasobów małych firm Zasoby dla twojej małej firmy Uzyskaj porady, bezpłatne szkolenia, produkty i narzędzia, które pomogą Twojej firmie rozwijać się. Pomoc i nauka w małych firmach Centrum zasobów małych firm Zasoby dla twojej małej firmy Uzyskaj porady, bezpłatne szkolenia, produkty i narzędzia, które pomogą Twojej firmie rozwijać się. Pomoc i nauka w małych firmach Co nowego Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot dla organizacji Copilot do użytku osobistego Microsoft 365 Poznaj produkty Microsoft Microsoft Store Profil konta Centrum pobierania Pomoc techniczna Microsoft Store Zwroty Śledzenie zamówienia Recykling Gwarancje handlowe Edukacja Microsoft Education Urządzenia dla instytucji edukacyjnych Microsoft Teams dla Instytucji Edukacyjnych Microsoft 365 Education Office Education Szkolenia i możliwości rozwoju dla nauczycieli Oferty dla uczniów i rodziców Azure dla uczniów Dla firm Rozwiązania zabezpieczające firmy Microsoft Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Dla programistów i specjalistów IT Deweloper Microsoft Microsoft Learn Pomoc techniczna do aplikacji z platformy handlowej opartych na AI Społeczność Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Firma Praca Informacje o firmie Microsoft Aktualności Ochrona prywatności Inwestorzy Zrównoważony rozwój Polski (Polska) Ikona rezygnacji z opcji prywatności Twoje opcje wyboru dotyczące prywatności Ikona rezygnacji z opcji prywatności Twoje opcje wyboru dotyczące prywatności Zasady prywatności dotyczące zdrowia użytkowników Skontaktuj się z Microsoft Ochrona prywatności Zarządzaj plikami cookie Zasady użytkowania Znaki towarowe Informacje o naszych reklamach EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:41 |
https://www.theverge.com/2022/11/8/23446821/microsoft-openai-github-copilot-class-action-lawsuit-ai-copyright-violation-training-data | The lawsuit against Microsoft, GitHub and OpenAI that could change the rules of AI copyright | The Verge Skip to main content The homepage The Verge The Verge logo. The Verge The Verge logo. Tech Reviews Science Entertainment AI CES Hamburger Navigation Button The homepage The Verge The Verge logo. Hamburger Navigation Button Navigation Drawer The Verge The Verge logo. Login / Sign Up close Close Search Tech Expand Amazon Apple Facebook Google Microsoft Samsung Business See all tech Gadgets Expand Laptops Phones TVs Headphones Speakers Wearables See all gadgets Reviews Expand Smart Home Reviews Phone Reviews Tablet Reviews Headphone Reviews See all reviews AI Expand OpenAI Anthropic See all AI Verge Shopping Expand Buying Guides Deals Gift Guides See all shopping Policy Expand Antitrust Politics Law Security See all policy Science Expand Space Energy Environment Health See all science Entertainment Expand TV Shows Movies Audio See all entertainment Gaming Expand Xbox PlayStation Nintendo See all gaming Streaming Expand Disney HBO Netflix YouTube Creators See all streaming Transportation Expand Electric Cars Autonomous Cars Ride-sharing Scooters See all transportation Features Verge Video Expand TikTok YouTube Instagram Podcasts Expand Decoder The Vergecast Version History Newsletters Expand The Verge Daily Installer Verge Deals Notepad Optimizer Regulator The Stepback Archives Store Subscribe Facebook Threads Instagram Youtube RSS The Verge The Verge logo. The lawsuit that could rewrite the rules of AI copyright Comments Drawer Comments Loading comments Getting the conversation ready... AI Close AI Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All AI News Close News Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All News Policy Close Policy Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All Policy The lawsuit that could rewrite the rules of AI copyright Microsoft, GitHub, and OpenAI are being sued for allegedly violating copyright law by reproducing open-source code using AI. But the suit could have a huge impact on the wider world of artificial intelligence. Microsoft, GitHub, and OpenAI are being sued for allegedly violating copyright law by reproducing open-source code using AI. But the suit could have a huge impact on the wider world of artificial intelligence. by James Vincent Close James Vincent Senior Reporter Last published Feb 16, 2024 Posts from this author will be added to your daily email digest and your homepage feed. Follow Follow See All by James Vincent Nov 8, 2022, 4:09 PM UTC Link Share The key question in the lawsuit is whether open-source code can be reproduced by AI without attached licenses. Credit: Getty Images James Vincent Close James Vincent Posts from this author will be added to your daily email digest and your homepage feed. Follow Follow See All by James Vincent is a senior reporter who has covered AI, robotics, and more for eight years at The Verge. Microsoft, its subsidiary GitHub, and its business partner OpenAI have been targeted in a proposed class action lawsuit alleging that the companies’ creation of AI-powered coding assistant GitHub Copilot relies on “software piracy on an unprecedented scale.” The case is only in its earliest stages but could have a huge effect on the broader world of AI, where companies are making fortunes training software on copyright-protected data. Copilot, which was unveiled by Microsoft-owned GitHub in June 2021, is trained on public repositories of code scraped from the web, many of which are published with licenses that require anyone reusing the code to credit its creators. Copilot has been found to regurgitate long sections of licensed code without providing credit — prompting this lawsuit that accuses the companies of violating copyright law on a massive scale. “This is the first class-action case in the US challenging the training and output of AI systems. It will not be the last.” “We are chal­leng­ing the legal­ity of GitHub Copi­lot,” said programmer and lawyer Matthew Butterick, who filed the lawsuit with the help of the San Francisco-based Joseph Saveri Law Firm, in a press statement. “This is the first step in what will be a long jour­ney. As far as we know, this is the first class-action case in the US chal­leng­ing the train­ing and out­put of AI sys­tems. It will not be the last. AI sys­tems are not exempt from the law. Those who cre­ate and oper­ate these sys­tems must remain account­able.” The lawsuit, which was filed last Friday, is in its early stages. In particular, the court has not yet certified the proposed class of programmers who have allegedly been harmed. But speaking to The Verge , Butterick and lawyers Travis Manfredi and Cadio Zirpoli of the Joseph Saveri Law Firm said they expected the case to have a huge impact on the wider world of generative AI. Microsoft and OpenAI are far from alone in scraping copyrighted material from the web to train AI systems for profit. Many text-to-image AI, like the open-source program Stable Diffusion, were created in exactly the same way. The firms behind these programs insist that their use of this data is covered in the US by fair use doctrine. But legal experts say this is far from settled law and that litigation like Butterick’s class action lawsuit could upend the tenuously defined status quo . To find out more about the motivations and reasoning behind the lawsuit, we spoke to Butterick (MB), Manfredi (TM), and Zirpoli (CZ), who explained why they think we’re in the Napster-era of AI and why letting Microsoft use other’s code without attribution could kill the open source movement. In response to a request for comment, GitHub said: “We’ve been committed to innovating responsibly with Copilot from the start, and will continue to evolve the product to best serve developers across the globe.” OpenAI and Microsoft had not replied to similar requests at the time of publication. This interview has been edited for clarity and brevity First, I want to talk about the reaction from the AI community a little bit, from people who are advocates for this technology. I found one comment that I think’s representative of one reaction to this case, which says, “Butterick’s goal here is to kill transformative ML use of data such as source code or images, forever.” What do you think about that, Matthew? Is that your goal? If not, what is? “AI systems are not magical black boxes that are exempt from the law.” Matthew Butterick: I think it’s really simple. AI systems are not magical black boxes that are exempt from the law, and the only way we’re going to have a responsible AI is if it’s fair and ethical for everyone. So the owners of these systems need to remain accountable. This isn’t a principle we’re making out of whole cloth and just applying to AI. It’s the same principle we apply to all kinds of products, whether it’s food, pharmaceuticals, or transportation. I feel sometimes that the backlash you get from the AI community — and you’re dealing with wonderful researchers, wonderful thinkers — they’re not acclimated to working in this sphere of regulation and safety. It’s always a challenge in technology because regulation moves behind innovation. But in the interim, cases like this fill that gap. That’s part of what a class action lawsuit is about: is testing these ideas and starting to create clarity. Do you think if you’re successful with your lawsuit that it will have a destructive effect on innovation in this domain, on the creation of generative AI models? We’re in the Napster-era of generative AI, says Butterick, with piracy fueling innovation MB: I hope it’s the opposite. I think in technology, we see over and over that products come out that skirt the edges of the law, but then someone comes by and finds a better way to do it. So, in the early 2000s, you had Napster, which everybody loved but was completely illegal. And today, we have things like Spotify and iTunes. And how did these systems arise? By companies making licensing deals and bringing in content legitimately. All the stakeholders came to the table and made it work, and the idea that a similar thing can’t happen for AI is, for me, a little catastrophic. We just saw an announcement recently of Shutterstock setting up a Contributors’ Fund for people whose images are used in training [generative AI], and maybe that will become a model for how other training is done. Me, I much prefer Spotify and iTunes, and I’m hoping that the next generation of these AI tools are better and fairer for everyone and makes everybody happier and more productive. I take it from your answers that you wouldn’t accept a settlement from Microsoft and OpenAI? MB: [ Laughs ] It’s only day one of the lawsuit... One section of the lawsuit I thought was particularly interesting was on the very close but murkily defined business relationship between Microsoft and OpenAI. You point out that in 2016 OpenAI said it would run its large-scale experiments on Microsoft’s cloud, that Microsoft has exclusive licenses for certain OpenAI products, and that Microsoft has invested a billion dollars in OpenAI, making it both OpenAI’s largest investor and service provider. What is the significance of this relationship, and why did you feel you needed to highlight it? Travis Manfredi: Well, I would say that Microsoft is trying to use as a perceived beneficial OpenAI as a shield to avoid liability. They’re trying to filter the research through this nonprofit to make it fair use, even though it’s probably not. So we want to show that whatever OpenAI started out as, it’s not that anymore. It’s a for-profit business. Its job is to make money for its investors. It may be controlled by a nonprofit [OpenAI Inc.], but the board of that nonprofit are all business people. We don’t know what their intentions are. But it doesn’t seem to be following the original mission of OpenAI. So we wanted to show — and hopefully discovery will reveal more information about this — that this is a collective scheme between Microsoft, OpenAI, and GitHub that is not as beneficial or as altruistic as they might have us believe. What do you fear will happen if Microsoft, GitHub, OpenAI, and other players in the industry building generative AI models are allowed to keep using other people’s data in this way? TM: Ultimately, it could be the end of open-source licenses altogether. Because if companies are not going to respect your licenses, what’s the point of even putting it on your code? If it’s going to be snapped up and spit back out without any attribution? We think open-source code has been tremendously beneficial to humanity and to the technology world, and we don’t think AI that doesn’t understand how to code and can only make probabilistic guesses, we don’t think that’s better than the innovation that human coders can deliver. “Someone comes along and says, ‘Let’s socialize the costs and privatize the profits.’” MB: Yeah, I really do think this is an existential threat to open source. And maybe it’s just my generation, but I’ve seen enough situations when there’s a nice, free community operating on the internet, and someone comes along and says, “Let’s socialize the costs and privatize the profits.” If you divorce the code from the creators, what does it mean? Let me give you one example. I spoke to an engineer in Europe who said, “Attribution is a really big deal to me because that’s how I get all my clients. I make open source software; people use my packages, see my name on it, and contact me, and I sell them more engineering or support.” He said, “If you take my attribution off, my career is over, and I can’t support my family, I can’t live.” And it really brings home that this is not a benign issue for a lot of programmers. But do you think there’s a case to be made that tools like Copilot are the future and that they are better for coders in general? MB: I love AI, and it’s been a dream of mine since I was an eight-year-old playing with a computer that we can teach these machines to reason like we do, and so I think this is a really interesting and wonderful field. But I can only go back to the Napster example: that [these systems] are just the first step, and no matter how much people thought Napster was terrific, it was also completely illegal, and we’ve done a lot better by bringing everyone to the table and making it fair for everybody. So, what is a remedy that you’d like to see implemented? Some people argue that there is no good solution, that the training datasets are too big, that the AI models are too complex, to really trace attribution and give credit. What do you think of that? Cadio Zirpoli: We’d like to see them train their AI in a manner which respects the licenses and provides attribution. I’ve seen on chat boards out there that there might be ways for people who don’t want that to opt out or opt in but to throw up your hands and say “it’s too hard, so just let Microsoft do whatever they want” is not a solution we’re willing to live with. Do you think this lawsuit could set precedence in other media of generative AI? We see similar complaints in text-to-image AI, that companies, including OpenAI, are using copyright-protected images without proper permission, for example. CZ: The simpler answer is yes. TM: The DMCA applies equally to all forms of copyrightable material, and images often include attribution; artists, when they post their work online, typically include a copyright notice or a creative commons license, and those are also being ignored by [companies creating] image generators. So what happens next with this lawsuit? I believe you need to be granted class-action status on this lawsuit for it to go ahead. What timeframe do you think that could happen on? CZ: Well, we expect Microsoft to bring a motion to dismiss our case. We believe we will be successful, and the case will proceed. We’ll engage in a period of discovery, and then we will move the court for class certification. The timing of that can vary widely with respect to different courts and different judges, so we’ll have to see. But we believe we have a meritorious case and that we will be successful not only overcoming the motion to dismiss but in getting our class certified. Follow topics and authors from this story to see more like this in your personalized homepage feed and to receive email updates. James Vincent Close James Vincent Senior Reporter Last published Feb 16, 2024 Posts from this author will be added to your daily email digest and your homepage feed. Follow Follow See All by James Vincent AI Close AI Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All AI Interview Close Interview Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All Interview Law Close Law Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All Law Microsoft Close Microsoft Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All Microsoft News Close News Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All News Policy Close Policy Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All Policy Report Close Report Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All Report Tech Close Tech Posts from this topic will be added to your daily email digest and your homepage feed. Follow Follow See All Tech Most Popular Most Popular Apple picks Google’s Gemini AI for its big Siri upgrade The Verge Awards at CES 2026 Tim Cook and Sundar Pichai are cowards Anker goes big with new whole home backup system Trump’s fundraisers asked Microsoft for its White House ballroom donation The Verge Daily A free daily digest of the news that matters most. Email (required) Sign Up By submitting your email, you agree to our Terms and Privacy Notice . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Advertiser Content From This is the title for the native ad More in AI UK pushes up a law criminalizing deepfake nudes in response to Grok Anthropic wants you to use Claude to ‘Cowork’ in latest AI agent push Google brings buy buttons to Gemini and AI search Google pulls AI overviews for some medical searches Google’s AI Inbox could be a glimpse of Gmail’s future AI is coming for collectibles next UK pushes up a law criminalizing deepfake nudes in response to Grok Jay Peters Jan 12 Anthropic wants you to use Claude to ‘Cowork’ in latest AI agent push Hayden Field Jan 12 Google brings buy buttons to Gemini and AI search Robert Hart Jan 12 Google pulls AI overviews for some medical searches Terrence O'Brien Jan 11 Google’s AI Inbox could be a glimpse of Gmail’s future Jay Peters Jan 11 AI is coming for collectibles next Dominic Preston Jan 9 Advertiser Content From This is the title for the native ad Top Stories Jan 12 Anthropic wants you to use Claude to ‘Cowork’ in latest AI agent push Jan 12 Anker goes big with new whole home backup system Jan 12 Apple picks Google’s Gemini AI for its big Siri upgrade Jan 12 The Stranger Things behind-the-scenes doc is a lot more boring than a secret episode Jan 12 Trump’s fundraisers asked Microsoft for its White House ballroom donation Jan 11 Google’s AI Inbox could be a glimpse of Gmail’s future The Verge The Verge logo. Facebook Threads Instagram Youtube RSS Contact Tip Us Community Guidelines Archives About Ethics Statement How We Rate and Review Products Cookie Settings Terms of Use Privacy Notice Cookie Policy Licensing FAQ Accessibility Platform Status © 2026 Vox Media , LLC. All Rights Reserved | 2026-01-13T09:29:41 |
https://ftp.gnu.org/old-gnu/gnunet/?C=M;O=A | Index of /old-gnu/gnunet Index of /old-gnu/gnunet Name Last modified Size Description Parent Directory - gnunet-fuse-0.8.0.tar.bz2 2008-06-14 04:40 80K gnunet-gtk-0.8.1a.tar.gz 2010-02-14 18:51 1.0M gnunet-fuse-0.9.3.tar.gz 2012-06-06 07:49 270K gnunet-gtk-0.9.5.tar.gz 2012-12-21 11:38 1.1M gnunet-fuse-0.10.0.tar.gz 2013-12-22 17:51 203K gnunet-0.10.0.tar.gz 2013-12-24 15:31 4.4M gnunet-gtk-0.10.0.tar.gz 2013-12-25 02:57 1.4M gnunet-gtk-0.10.1.tar.gz 2014-04-08 07:21 1.5M gnunet-0.10.1.tar.gz 2014-04-08 07:45 4.8M gnurl-7.57.0.tar.xz 2017-12-09 11:36 2.2M gnurl-7.56.1.tar.xz 2017-12-10 06:48 2.2M gnurl-7.56.1-2.tar.xz 2017-12-10 06:50 2.2M gnurl-7.56.1.1.tar.xz 2017-12-10 06:52 2.2M gnurl-7.56.0.tar.xz 2017-12-10 06:53 2.2M gnurl-7.55.1.tar.bz2 2017-12-10 06:54 2.0M gnurl-7.55.1.diff 2017-12-10 06:54 202K gnurl-7.55.1-4.tar.bz2 2017-12-10 06:58 2.7M gnurl-7.55.1-3.tar.bz2 2017-12-10 06:58 2.0M gnurl-7.55.0.diff 2017-12-10 07:00 151K gnurl-7.55.0.tar.bz2 2017-12-10 07:01 2.0M gnurl-7.54.1.diff 2017-12-10 07:01 148K gnurl-7.54.1.tar.bz2 2017-12-10 07:02 1.8M gnurl-7.54.0.tar.bz2 2017-12-10 07:03 1.8M gnurl-7.53.1.diff 2017-12-10 07:03 148K gnurl-7.53.1.tar.xz 2017-12-10 07:04 3.0M gnurl-7_52_1.tar.bz2 2017-12-10 07:06 3.2M gnurl-7_52_1.diff 2017-12-10 07:07 34K gnurl-7_52_0.tar.bz2 2017-12-10 07:08 2.9M gnurl-7_52_0.diff 2017-12-10 07:09 34K gnurl-7.57.0.tar.bz2 2017-12-10 07:10 2.6M gnurl-7.56.1.tar.bz2 2017-12-10 07:11 2.6M gnurl-7.56.1.1.tar.bz2 2017-12-10 07:13 2.6M gnurl-7.56.1-2.tar.bz2 2017-12-10 07:14 2.6M gnurl-7.56.0.tar.bz2 2017-12-10 07:15 2.7M gnurl-7.53.1.zip 2017-12-10 07:16 6.1M gnurl-7.53.1.tar.bz2 2017-12-10 07:17 3.0M gnurl-7_48_0.diff 2017-12-13 16:00 253K gnurl-7_48_0.tar.bz2 2017-12-13 16:01 3.0M gnurl-7_50_1.diff 2017-12-13 16:01 261K gnurl-7_50_2-1.tar.bz2 2017-12-13 16:02 2.8M gnurl-7_50_2.diff 2017-12-13 16:03 30K gnurl-7_50_2.tar_0.bz2 2017-12-13 16:04 2.8M gnurl-7_50_3.diff 2017-12-13 16:04 30K gnurl-7_50_3.tar.bz2 2017-12-13 16:05 4.4M gnurl-7_51_0.diff 2017-12-13 16:06 30K gnurl-7_51_0.tar.bz2 2017-12-13 16:07 4.5M gnurl-7.58.0.tar.xz 2018-01-27 10:10 2.2M gnurl-7.58.0.tar.bz2 2018-01-27 10:11 2.7M gnurl-7.59.0.tar.xz 2018-04-22 16:15 2.2M gnurl-7.59.0.tar.gz 2018-04-22 16:17 3.7M gnurl-7.60.0.tar.Z 2018-05-23 07:53 6.4M gnurl-7.60.0.tar.gz 2018-05-23 07:53 3.7M gnunet-gtk-0.11.0pre66.tar.gz 2018-06-05 17:55 1.5M gnunet-fuse-0.11.0pre66.tar.gz 2018-06-05 17:55 216K gnunet-0.11.0pre66.tar.gz 2018-06-06 07:00 7.1M gnunet-0.11.0pre666.tar.gz 2018-06-06 07:00 7.1M gnurl-7.61.0.tar.Z 2018-08-05 06:58 6.4M gnurl-7.61.0.tar.gz 2018-08-05 06:59 3.7M gnurl-7.61.1.tar.Z 2018-09-11 08:02 6.4M gnurl-7.61.1.tar.gz 2018-09-11 08:05 3.8M gnurl-7.62.0.tar.gz 2018-11-24 06:29 3.8M gnurl-7.62.0.tar.Z 2018-11-24 06:31 6.5M gnurl-7.63.0.tar.gz 2019-01-13 21:09 3.5M gnurl-7.63.0.tar.Z 2019-01-13 21:11 6.0M gnurl-7.63.0.pax.Z 2019-01-13 21:13 6.0M gnurl-7.64.0.pax.Z 2019-02-25 15:00 6.0M gnurl-7.64.0.tar.gz 2019-02-25 15:01 3.5M gnurl-7.64.0.tar.Z 2019-02-25 15:02 6.0M gnunet-0.11.0.tar.gz 2019-02-28 06:29 7.2M gnunet-gtk-0.11.0.tar.gz 2019-02-28 06:29 1.6M gnunet-fuse-0.11.0.tar.gz 2019-02-28 06:29 211K gnunet-0.11.1.tar.gz 2019-04-03 10:14 7.2M gnunet-0.11.2.tar.gz 2019-04-04 06:41 7.2M gnunet-0.11.3.tar.gz 2019-04-07 08:42 7.2M gnurl-7.64.1.pax.Z 2019-04-29 14:19 6.0M gnurl-7.64.1.tar.gz 2019-04-29 14:20 3.5M gnurl-7.64.1.tar.Z 2019-04-29 14:21 6.0M gnunet-0.11.4.tar.gz 2019-05-12 07:37 7.2M gnurl-7.65.0.pax.Z 2019-05-31 06:18 5.8M gnurl-7.65.0.tar.gz 2019-05-31 06:19 3.3M gnurl-7.65.0.tar.Z 2019-05-31 06:21 5.8M gnurl-7.65.0.sum.txt 2019-05-31 06:21 900 gnunet-0.11.5.tar.gz 2019-06-05 12:45 7.3M gnunet-gtk-0.11.5.tar.gz 2019-06-05 12:45 1.6M gnurl-7.65.1.sum.txt 2019-06-07 14:14 900 gnurl-7.65.1.pax.Z 2019-06-07 14:15 5.8M gnurl-7.65.1.tar.gz 2019-06-07 14:16 3.3M gnurl-7.65.1.tar.Z 2019-06-07 14:18 5.8M gnunet-0.11.6.tar.gz 2019-07-24 12:35 7.3M gnurl-7.65.3.sum.txt 2019-08-15 09:01 900 gnurl-7.65.3.pax.Z 2019-08-15 09:02 5.8M gnurl-7.65.3.tar.gz 2019-08-15 09:03 3.3M gnurl-7.65.3.tar.Z 2019-08-15 09:05 5.8M gnurl-7.66.0.sum.txt 2019-09-13 11:15 900 gnurl-7.66.0.pax.Z 2019-09-13 11:16 5.9M gnurl-7.66.0.tar.gz 2019-09-13 11:17 3.4M gnurl-7.66.0.tar.Z 2019-09-13 11:18 5.9M gnunet-0.11.7.tar.gz 2019-10-27 13:21 7.0M gnunet-gtk-0.11.7.tar.gz 2019-10-27 14:50 1.6M gnunet-0.11.8.tar.gz 2019-10-30 07:35 7.0M gnurl-7.67.0.sum.txt 2019-11-18 13:03 900 gnurl-7.67.0.pax.Z 2019-11-18 13:04 5.9M gnurl-7.67.0.tar.gz 2019-11-18 13:05 3.5M gnurl-7.67.0.tar.Z 2019-11-18 13:06 5.9M gnunet-fuse-0.11.8.tar.gz 2019-11-22 11:55 216K gnunet-0.12.0.tar.gz 2019-12-19 20:08 7.2M gnunet-fuse-0.12.0.tar.gz 2019-12-19 20:20 215K gnunet-gtk-0.12.0.tar.gz 2019-12-19 20:20 1.5M gnunet-0.12.1.tar.gz 2019-12-25 07:11 7.2M gnunet-0.12.2.tar.gz 2020-01-13 09:16 7.2M gnurl-7.69.1.sum.txt 2020-04-07 12:20 900 gnurl-7.69.1.pax.Z 2020-04-07 12:21 5.9M gnurl-7.69.1.tar.gz 2020-04-07 12:23 3.4M gnurl-7.69.1.tar.Z 2020-04-07 12:24 5.9M gnurl-7.70.0.sum.txt 2020-04-30 15:43 900 gnurl-7.70.0.pax.Z 2020-04-30 15:44 5.7M gnurl-7.70.0.tar.gz 2020-04-30 15:45 3.2M gnurl-7.70.0.tar.Z 2020-04-30 15:46 5.7M gnunet-0.13.0.tar.gz 2020-07-07 12:45 7.2M gnunet-gtk-0.13.0.tar.gz 2020-07-07 12:55 1.5M gnunet-fuse-0.13.0.tar.gz 2020-07-07 12:57 216K gnunet-0.13.1.tar.gz 2020-07-12 12:39 7.2M gnunet-gtk-0.13.1.tar.gz 2020-07-12 12:39 1.5M gnunet-0.13.2.tar.gz 2020-08-14 03:39 7.2M gnunet-0.13.3.tar.gz 2020-09-06 08:13 7.4M Apache/2.4.52 (Trisquel_GNU/Linux) Server at ftp.gnu.org Port 443 | 2026-01-13T09:29:41 |
https://www.atlassian.com/ru/software/jira/service-management/features/asset-and-configuration-management | Управление активами и конфигурацией с помощью Jira | Atlassian Close Хотите открыть эту страницу на своем языке ? Все языки Выберите язык 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Получить бесплатно Приложения Service Collection Jira Service Management Управление обслуживанием клиентов Активы Service Collection Back Цены Дополнительно + Меньше - Получить бесплатно Back Получить бесплатно Управление ресурсами и конфигурацией С помощью приложения «Активы» можно получить наглядное представление всех зависимостей, чтобы вы могли управлять ресурсами, элементами конфигурации (CI), быстро разрешать инциденты и минимизировать риски, связанные с изменениями. Попробовать Познакомьтесь с «Активами» Посмотреть видео Место для хранения важных данных В отличие от используемых ранее баз данных, приложение «Активы» предлагает гибкую и открытую структуру данных. Так команды смогут управлять критически важными ресурсами и подключать их к запросам, инцидентам, изменениям и т. д. Отслеживайте самое важное Объедините все свои корпоративные активы в гибкой базе данных — от элементов конфигурации, аппаратного и программного обеспечения до людей, роялей и рыб (правда-правда). Готовые шаблоны помогут быстрее начать работу. Свяжите активы с работой Связывайте объекты в разделе «Активы» с заявками в службу поддержки, задачами по инцидентам, запросами на изменения и т. д. Повышайте наглядность и ускоряйте работу во всех сферах — ИТ, отделе кадров, административно-хозяйственном отделе и других. Оптимальные решения Обеспечьте полную прозрачность и контроль активов для снижения рисков и улучшения операционной деятельности. Теперь это стало доступно с помощью новых гибких отчетов и дашбоардов для углубленной аналитики и принятия более взвешенных и быстрых решений. Добавьте в «Активы» полные, актуальные и верные данные Диспетчер данных об активах упрощает интеграцию, согласование и анализ данных из нескольких источников, благодаря чему у вас появляются надежные сведения для принятия разумных решений. Подробнее Функции управления ресурсами и конфигурацией Автоматизация Забудьте об отслеживании владельцев или обновлении электронных таблиц. Автоматизируйте ввод данных из задач Jira, чтобы поддерживать необходимую информацию об активах в актуальном состоянии. Запросы Выполняйте запросы к объектам функции «Активы» для проведения аудита, управления затратами и выявления причин проблем. Шаблоны Быстро приступайте к работе с помощью готовых шаблонов схем, позволяющих структурировать базу данных для использования в сферах ИТ, отделе кадров, административно-хозяйственном отделе и других. Discovery Выявите активы с поддержкой IP, извлекайте информацию о ключевых атрибутах и зависимостях, а также отслеживайте любые изменения, чтобы оставаться в курсе событий. Интеграции Беспрепятственно переносите важные данные в «Активы» с помощью более чем 30 адаптеров, в том числе для неструктурированных файлов и баз данных SQL. Отчеты Получайте актуальную аналитику из данных об активах, отслеживайте их состояние, выявляйте пробелы в соблюдении нормативных требований и риски безопасности, а также получайте доступ к важным финансовым данным. «Функция „Активы“ позволяет сохранять предсказуемость, а также планировать покупку лицензий и затраты на программное обеспечение». Дамир Прусак Вице-президент по инжинирингу, Infobip Узнайте больше Часто задаваемые вопросы В чем разница между версиями функции «Активы» для Jira Service Management Cloud, Data Center и приложением «Активы»? Подробнее о возможностях функции «Активы» в зависимости от используемого плана см. в этой сравнительной таблице . Можно ли использовать раздел «Активы» с разделами Jira? Да. Объекты в «Активах» можно связывать с задачами Jira, если в этом же экземпляре присутствует активная лицензия Service Collection с планом Standard. Зачем переходить с другого инструмента управления CMDB/ресурсами? Перемещение базы данных CMDB в «Активы», приложение в составе подборки Service Collection, дает следующие возможности. Позволяет оптимизировать работу, поскольку вся информация об ITSM (запросы, инциденты, изменения и проблемы) и CMDB находится в одном инструменте. Предоставляет более подробный контекст о связи между активами и элементами конфигурации, а также между инцидентами и изменениями, что позволяет командам разработчиков и командам по эксплуатации быстрее находить основную причину проблемы и управлять рисками, чтобы эффективнее выполнять развертывания. Позволяет сократить затраты, поскольку другие поставщики CMDB обходятся дороже. Повышает гибкость хранения любых типов запасов, активов или записей — не только в сфере ИТ. Предлагает ли Atlassian инструменты для поиска и обнаружения активов? Да, с помощью базовых функций поиска можно обнаруживать активы и элементы конфигурации, подключенные к вашей локальной сети, и извлекать подробную информацию о каждом из них. Мы также предлагаем интеграцию с ведущими решениями для обнаружения, такими как Lansweeper и Flexera, для поиска и импорта устройств в приложение «Активы». Как данные импортируются в раздел «Активы»? Используя «Активы», пользователи могут использовать диспетчер данных и его встроенную функцию импорта схем. Подробности здесь: Узнайте больше о диспетчере данных в приложении «Активы» Подробнее об инструментах адаптации Настройте диспетчер данных в приложении «Активы» Переместите данные в диспетчер данных для создания необработанных данных Удалите ненужные значения для получения преобразованных данных Удалите ненужные записи для создания очищенных данных Согласуйте источники данных для создания объектов диспетчера данных Импортируйте в схему «Активы» для создания объектов схемы Что можно хранить в разделе «Активы»? Что угодно. Честно! Традиционные ИТ-ресурсы, такие как аппаратное обеспечение? ✅ Элементы конфигурации? ✅ Записи о людях? ✅ Рыб? Если это важно для вас, это важно и для нас ✅ Раздел «Активы» гибко подстраивается под ваши нужды. Просто создайте подходящий для вас тип объектов и схему, и вы на верном пути. Материалы по управлению ресурсами и конфигурацией Демо Управление запасами в разделе «Активы» Смотреть демонстрацию Технический документ Руководство по управлению ресурсами и конфигурацией для ITSM Подробнее электронная книга Эволюция активов: разумный подход к созданию бизнес-ценности Подробнее Продуманные решения начинаются с качественных данных об активах Попробовать бесплатно Компания Вакансии События Блоги Связи с инвесторами Atlassian Foundation Материалы для СМИ Свяжитесь с нами продукты Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Посмотреть все продукты Ресурсы Техническая поддержка Покупка и лицензирование Сообщество Atlassian База знаний Marketplace Мой аккаунт Заявка в поддержку Обучение Партнеры Обучение и сертификация Документация Ресурсы для разработчиков Сервисы Enterprise Смотреть все ресурсы © Atlassian, 2025 г. Политика конфиденциальности Условия использования Impressum Выберите язык Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://www.atlassian.com/es/industries/professional-services | Versatile Software for Professional Services | Atlassian Close ¿Quieres ver esta página en tu idioma ? Todos los idiomas Elige tu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Obtener gratis Productos Contenido destacado Desarrolladores Gestores de productos Profesionales de TI Equipos empresariales Equipos de liderazgo Contenido destacado Desarrolladores Gestores de productos Profesionales de TI Equipos empresariales Equipos de liderazgo Ver todas las aplicaciones Contenido destacado Aplicaciones funcionales Jira Gestión de proyectos flexible Confluence Espacio de trabajo colaborativo para el conocimiento Jira Service Management Prestación de servicios de alta velocidad Atlassian Collections Potencia el trabajo en equipo sin problemas Jira • Confluence • Loom • Rovo Optimiza la estrategia y los resultados con confianza Focus • Talent • Align Presta servicio a alta velocidad Jira Service Management • Customer Service Management • Activos • Rovo Lanza software de alta calidad rápidamente Rovo Dev • DX • Pipelines • Bitbucket • Compass Con tecnología de Rovo Aplicaciones con tecnología de IA, impulsadas por los conocimientos de tu equipo. Desarrolladores Jira Gestión de proyectos flexible Compass Catálogo de software para equipos Pipelines Automatización de CI/CD escalable Bitbucket Código fuente y CI/CD DX (Adquisición pendiente) Mide la productividad y el impacto de la IA Rovo Dev Agentic AI para desarrolladores Lanza software de alta calidad rápidamente Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo Aplicaciones con tecnología de IA, impulsadas por los conocimientos de tu equipo. Gestores de productos Jira Gestión de proyectos flexible Confluence Los conocimientos, todos en un mismo sitio Jira Product Discovery NUEVO Registra y da prioridad a las ideas Potencia el trabajo en equipo sin problemas Jira • Confluence • Loom • Rovo Rovo Aplicaciones con tecnología de IA, impulsadas por los conocimientos de tu equipo. Profesionales de TI Jira Service Management Prestación de servicios de alta velocidad Guard NUEVO Seguridad en la nube mejorada Rovo Aplicaciones con tecnología de IA, impulsadas por los conocimientos de tu equipo. Equipos empresariales Jira Gestión de proyectos flexible Confluence Los conocimientos, todos en un mismo sitio Trello Trabajo visualizado y organizado Loom NUEVO Actualizaciones de vídeo rápidas y asíncronas Jira Service Management Prestación de servicios de alta velocidad Customer Service Management Customer experiences reimagined Potencia el trabajo en equipo sin problemas Jira • Confluence • Loom • Rovo Rovo Aplicaciones con tecnología de IA, impulsadas por los conocimientos de tu equipo. Equipos de liderazgo Focus NUEVO Planificación estratégica a escala empresarial Talent NUEVO Conocimiento sobre la planificación de la plantilla Jira Align Valor y planificación del trabajo en toda la empresa Optimiza la estrategia y los resultados con confianza Focus • Talent • Align Rovo Aplicaciones con tecnología de IA, impulsadas por los conocimientos de tu equipo. Back Soluciones Soluciones Por caso práctico Colaboración de Equipos Estrategia y planificación Gestión de servicios Desarrollo de software Por equipo software Marketing TI Por tamaño Enterprise Negocios pequeños Startup Organizaciones sin fines de lucro Por sector Comercio minorista Telecomunicaciones Servicios profesionales Gobierno Rovo Aplicaciones con tecnología de IA, impulsadas por los conocimientos de tu equipo. Back ¿Por qué Atlassian? ¿Por qué Atlassian? Sistema de trabajo Novedad El modelo de Atlassian para la colaboración entre equipos Integraciones Conecta miles de aplicaciones con tus productos de Atlassian Clientes Casos prácticos e historias impulsadas por el trabajo en equipo FedRAMP Soluciones compatibles con el sector público Resistencia Infraestructura de alto rendimiento y nivel empresarial Plataforma Nuestra plataforma profundamente integrada, segura y fiable Trust Center Garantiza la seguridad, el cumplimiento y disponibilidad de tus datos Back Recursos Recursos Atención al cliente Pregunta, informa de errores y envíanos tus comentarios Buscar un Partner Consultoría, formación y soporte de personalización de productos Atlassian Ascend Recursos y soporte para tu transformación Comunidad Aprende, conecta y crece con la Comunidad de Atlassian Soporte Dudas generales Asesoramiento sobre productos Soporte por parte de partners Asistencia para empresas Servicio técnico Precios y facturación Soporte para desarrolladores Compra y licencia Recursos Gestión de proyectos Agile Atlassian Learning Empieza ya Colaboración en proyectos Manual de estrategias del equipo Documentación del producto Back Enterprise Más + Menos - Obtener gratis Jira Gestión de proyectos flexible Jira Service Management Prestación de servicios de alta velocidad Confluence Los conocimientos, todos en un mismo sitio Ver todos los productos Obtener gratis Back Obtener gratis Conoce los secretos de la transformación con la nube y la IA. Echa un vistazo a nuestro seminario web para obtener datos relevantes y estrategias basadas en casos reales. Ver ahora Flexible project management tools for professional services From accounting firms to design agencies, legal practices, and everything in between, Atlassian’s project management and collaboration software empowers professional services businesses to deliver exceptional service to their clients. Versatile collaboration solutions Atlassian’s adaptable project management tools help professional services teams streamline their work and improve efficiency so they can deliver better results, faster. Project management Customer service Document & knowledge sharing Operations Project management Customer service Document & knowledge sharing Operations Project management Atlassian tools like Jira and Confluence allow you to manage projects, tasks, and workflows efficiently, ensuring all work is accurately tracked, organized, and delivered on time. Learn about Jira Customer service Improve customer satisfaction by creating status-sensitive tickets, service level agreements and custom workflows to identify and resolve customer service inquiries with Jira Service Management. Explore Customer Service Document & knowledge sharing Securely create, organize, share, and manage documents in one place with Confluence. Facilitate collaboration and streamline information access for your team. Explore team collaboration Operations Manage inventory, streamline operations and simplify procurement with Jira's flexible platform and comprehensive features. Explore operations Get started faster with templates Pre-built templates for professional services provide the springboard you need to build customized solutions for your business’s specific needs. Jira Jira Project management Manage activities for completing a business project. Jira Service Management Customer service management Deliver great service to external customers, fast. Jira Procurement Track all purchases from request to receipt. Confluence Email drip campaign Keep the details of your email sends organized and the results clear for your team. Explore more templates Over 1,000 trusted integrations Tailor Atlassian products to meet the needs of your professional services team with a variety of integrations and applications. Explore the Marketplace Everything professional services teams need to succeed Streamlined collaboration Reduce context switching, shorten feedback loops, and increase visibility for your team and clients alike by centralizing projects, tasks, and collaboration in a single, integrated platform. Comprehensive client management Atlassian’s versatile set of tools and templates provides everything you need to ensure success throughout every stage of the customer lifecycle. Flexible solutions Atlassian solutions are easily customizable to your unique business needs. Build the best solution for your team so you can deliver value to every one of your clients. Powerful reporting and analytics Built-in reporting and analytics capabilities breakdown silos with customizable and interactive data visualizations. Make data-informed decisions faster. Automate workflows & processes Low-code and no-code solutions make it easy to automate your workflows and processes so you can focus on important client work. Cross-product automation Atlassian products seamlessly integrate with a wide variety of other tools and systems to better support the unique needs of your business. Professional services teams love Atlassian 1/3 “With Atlassian, onshore and offshore teams are working together to focus on product goals.” Fabien Lamaison Head of Strategy and Innovation, Capgemini See Capgemini’s story 2/3 “With Atlassian, it’s easy to get started and spin up a solution. I also loved the idea of having a self-serve app marketplace.” Wendy Stockholm Director of BizTech, InVision See InVision’s Story 3/3 “Whether someone is in the office, working from home, or working on-site with a client, everyone can share context and information through Trello.” Sumeet Moghe Product Manager, Thoughtworks See ThoughtWorks’ Story ← → Recognized as a leader by industry experts Leader in the Gartner® Magic Quadrant™ for IT Service Management Platforms Leader in the Forrester 2021 WaveTM for Enterprise Service Management Secure & compliant Atlassian products are backed by industry-accepted certifications and comply with industry standards so professional services teams can feel confident their company and customer data remains secure. Explore the Atlassian Trust Center Professional services resources Browse white papers, case studies, reports and more to get all the information you need. Demo Jira's on-demand product demo Guide Common scaling challenges blog What your industry says about your cloud migration Learn more about Jira Transform the way you work Join thousands of professional services businesses already using Atlassian’s powerful suite of products. Compañía Resumen Eventos Blogs Relaciones con los inversores Atlassian Foundation Kit de prensa Ponte en contacto con nosotros. Productos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos los productos Recursos Servicio técnico Compra y licencia Comunidad de Atlassian Base de conocimientos Marketplace Mi cuenta Crear tique de asistencia Tutorial Socios Formación y certificación Documentación Recursos para desarrolladores Servicios empresariales Ver todos los recursos Copyright © 2025 Atlassian Política de privacidad Términos Impressum Selecciona un idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://git-scm.com/book/id/v2/Git-Basics-Working-with-Remotes | Git - Working with Remotes About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.5 Git Basics - Working with Remotes Working with Remotes To be able to collaborate on any Git project, you need to know how to manage your remote repositories. Remote repositories are versions of your project that are hosted on the Internet or network somewhere. You can have several of them, each of which generally is either read-only or read/write for you. Collaborating with others involves managing these remote repositories and pushing and pulling data to and from them when you need to share work. Managing remote repositories includes knowing how to add remote repositories, remove remotes that are no longer valid, manage various remote branches and define them as being tracked or not, and more. In this section, we’ll cover some of these remote-management skills. Showing Your Remotes To see which remote servers you have configured, you can run the git remote command. It lists the shortnames of each remote handle you’ve specified. If you’ve cloned your repository, you should at least see origin – that is the default name Git gives to the server you cloned from: $ git clone https://github.com/schacon/ticgit Cloning into 'ticgit'... remote: Reusing existing pack: 1857, done. remote: Total 1857 (delta 0), reused 0 (delta 0) Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done. Resolving deltas: 100% (772/772), done. Checking connectivity... done. $ cd ticgit $ git remote origin You can also specify -v , which shows you the URLs that Git has stored for the shortname to be used when reading and writing to that remote: $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) If you have more than one remote, the command lists them all. For example, a repository with multiple remotes for working with several collaborators might look something like this. $ cd grit $ git remote -v bakkdoor https://github.com/bakkdoor/grit (fetch) bakkdoor https://github.com/bakkdoor/grit (push) cho45 https://github.com/cho45/grit (fetch) cho45 https://github.com/cho45/grit (push) defunkt https://github.com/defunkt/grit (fetch) defunkt https://github.com/defunkt/grit (push) koke git://github.com/koke/grit.git (fetch) koke git://github.com/koke/grit.git (push) origin git@github.com:mojombo/grit.git (fetch) origin git@github.com:mojombo/grit.git (push) This means we can pull contributions from any of these users pretty easily. We may additionally have permission to push to one or more of these, though we can’t tell that here. Notice that these remotes use a variety of protocols; we’ll cover more about this in Getting Git on a Server . Adding Remote Repositories I’ve mentioned and given some demonstrations of adding remote repositories in previous sections, but here is how to do it explicitly. To add a new remote Git repository as a shortname you can reference easily, run git remote add [shortname] [url] : $ git remote origin $ git remote add pb https://github.com/paulboone/ticgit $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) pb https://github.com/paulboone/ticgit (fetch) pb https://github.com/paulboone/ticgit (push) Now you can use the string pb on the command line in lieu of the whole URL. For example, if you want to fetch all the information that Paul has but that you don’t yet have in your repository, you can run git fetch pb : $ git fetch pb remote: Counting objects: 43, done. remote: Compressing objects: 100% (36/36), done. remote: Total 43 (delta 10), reused 31 (delta 5) Unpacking objects: 100% (43/43), done. From https://github.com/paulboone/ticgit * [new branch] master -> pb/master * [new branch] ticgit -> pb/ticgit Paul’s master branch is now accessible locally as pb/master – you can merge it into one of your branches, or you can check out a local branch at that point if you want to inspect it. (We’ll go over what branches are and how to use them in much more detail in Git Branching .) Fetching and Pulling from Your Remotes As you just saw, to get data from your remote projects, you can run: $ git fetch [remote-name] The command goes out to that remote project and pulls down all the data from that remote project that you don’t have yet. After you do this, you should have references to all the branches from that remote, which you can merge in or inspect at any time. If you clone a repository, the command automatically adds that remote repository under the name “origin”. So, git fetch origin fetches any new work that has been pushed to that server since you cloned (or last fetched from) it. It’s important to note that the git fetch command pulls the data to your local repository – it doesn’t automatically merge it with any of your work or modify what you’re currently working on. You have to merge it manually into your work when you’re ready. If you have a branch set up to track a remote branch (see the next section and Git Branching for more information), you can use the git pull command to automatically fetch and then merge a remote branch into your current branch. This may be an easier or more comfortable workflow for you; and by default, the git clone command automatically sets up your local master branch to track the remote master branch (or whatever the default branch is called) on the server you cloned from. Running git pull generally fetches data from the server you originally cloned from and automatically tries to merge it into the code you’re currently working on. Pushing to Your Remotes When you have your project at a point that you want to share, you have to push it upstream. The command for this is simple: git push [remote-name] [branch-name] . If you want to push your master branch to your origin server (again, cloning generally sets up both of those names for you automatically), then you can run this to push any commits you’ve done back up to the server: $ git push origin master This command works only if you cloned from a server to which you have write access and if nobody has pushed in the meantime. If you and someone else clone at the same time and they push upstream and then you push upstream, your push will rightly be rejected. You’ll have to pull down their work first and incorporate it into yours before you’ll be allowed to push. See Git Branching for more detailed information on how to push to remote servers. Inspecting a Remote If you want to see more information about a particular remote, you can use the git remote show [remote-name] command. If you run this command with a particular shortname, such as origin , you get something like this: $ git remote show origin * remote origin Fetch URL: https://github.com/schacon/ticgit Push URL: https://github.com/schacon/ticgit HEAD branch: master Remote branches: master tracked dev-branch tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) It lists the URL for the remote repository as well as the tracking branch information. The command helpfully tells you that if you’re on the master branch and you run git pull , it will automatically merge in the master branch on the remote after it fetches all the remote references. It also lists all the remote references it has pulled down. That is a simple example you’re likely to encounter. When you’re using Git more heavily, however, you may see much more information from git remote show : $ git remote show origin * remote origin URL: https://github.com/my-org/complex-project Fetch URL: https://github.com/my-org/complex-project Push URL: https://github.com/my-org/complex-project HEAD branch: master Remote branches: master tracked dev-branch tracked markdown-strip tracked issue-43 new (next fetch will store in remotes/origin) issue-45 new (next fetch will store in remotes/origin) refs/remotes/origin/issue-11 stale (use 'git remote prune' to remove) Local branches configured for 'git pull': dev-branch merges with remote dev-branch master merges with remote master Local refs configured for 'git push': dev-branch pushes to dev-branch (up to date) markdown-strip pushes to markdown-strip (up to date) master pushes to master (up to date) This command shows which branch is automatically pushed to when you run git push while on certain branches. It also shows you which remote branches on the server you don’t yet have, which remote branches you have that have been removed from the server, and multiple branches that are automatically merged when you run git pull . Removing and Renaming Remotes If you want to rename a reference you can run git remote rename to change a remote’s shortname. For instance, if you want to rename pb to paul , you can do so with git remote rename : $ git remote rename pb paul $ git remote origin paul It’s worth mentioning that this changes your remote branch names, too. What used to be referenced at pb/master is now at paul/master . If you want to remove a remote for some reason – you’ve moved the server or are no longer using a particular mirror, or perhaps a contributor isn’t contributing anymore – you can use git remote rm : $ git remote rm paul $ git remote origin prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://git-scm.com/book/zh/v2/%e5%88%86%e5%b8%83%e5%bc%8f-Git-%e5%90%91%e4%b8%80%e4%b8%aa%e9%a1%b9%e7%9b%ae%e8%b4%a1%e7%8c%ae | Git - 向一个项目贡献 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 起步 1.1 关于版本控制 1.2 Git 简史 1.3 Git 是什么？ 1.4 命令行 1.5 安装 Git 1.6 初次运行 Git 前的配置 1.7 获取帮助 1.8 总结 2. Git 基础 2.1 获取 Git 仓库 2.2 记录每次更新到仓库 2.3 查看提交历史 2.4 撤消操作 2.5 远程仓库的使用 2.6 打标签 2.7 Git 别名 2.8 总结 3. Git 分支 3.1 分支简介 3.2 分支的新建与合并 3.3 分支管理 3.4 分支开发工作流 3.5 远程分支 3.6 变基 3.7 总结 4. 服务器上的 Git 4.1 协议 4.2 在服务器上搭建 Git 4.3 生成 SSH 公钥 4.4 配置服务器 4.5 Git 守护进程 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第三方托管的选择 4.10 总结 5. 分布式 Git 5.1 分布式工作流程 5.2 向一个项目贡献 5.3 维护项目 5.4 总结 6. GitHub 6.1 账户的创建和配置 6.2 对项目做出贡献 6.3 维护项目 6.4 管理组织 6.5 脚本 GitHub 6.6 总结 7. Git 工具 7.1 选择修订版本 7.2 交互式暂存 7.3 贮藏与清理 7.4 签署工作 7.5 搜索 7.6 重写历史 7.7 重置揭密 7.8 高级合并 7.9 Rerere 7.10 使用 Git 调试 7.11 子模块 7.12 打包 7.13 替换 7.14 凭证存储 7.15 总结 8. 自定义 Git 8.1 配置 Git 8.2 Git 属性 8.3 Git 钩子 8.4 使用强制策略的一个例子 8.5 总结 9. Git 与其他系统 9.1 作为客户端的 Git 9.2 迁移到 Git 9.3 总结 10. Git 内部原理 10.1 底层命令与上层命令 10.2 Git 对象 10.3 Git 引用 10.4 包文件 10.5 引用规范 10.6 传输协议 10.7 维护与数据恢复 10.8 环境变量 10.9 总结 A1. 附录 A: 在其它环境中使用 Git A1.1 图形界面 A1.2 Visual Studio 中的 Git A1.3 Visual Studio Code 中的 Git A1.4 IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 中的 Git A1.5 Sublime Text 中的 Git A1.6 Bash 中的 Git A1.7 Zsh 中的 Git A1.8 PowerShell 中的 Git A1.9 总结 A2. 附录 B: 在你的应用中嵌入 Git A2.1 命令行 Git 方式 A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. 附录 C: Git 命令 A3.1 设置与配置 A3.2 获取与创建项目 A3.3 快照基础 A3.4 分支与合并 A3.5 项目分享与更新 A3.6 检查与比较 A3.7 调试 A3.8 补丁 A3.9 邮件 A3.10 外部系统 A3.11 管理 A3.12 底层命令 2nd Edition 5.2 分布式 Git - 向一个项目贡献 向一个项目贡献 描述如何向一个项目贡献的主要困难在于完成贡献有很多不同的方式。 因为 Git 非常灵活，人们可以通过不同的方式来一起工作，所以描述应该如何贡献并不是非常准确——每一个项目都有一点儿不同。 影响因素包括活跃贡献者的数量、选择的工作流程、提交权限与可能包含的外部贡献方法。 第一个影响因素是活跃贡献者的数量——积极地向这个项目贡献代码的用户数量以及他们的贡献频率。 在许多情况下，你可能会有两三个开发者一天提交几次，对于不活跃的项目可能更少。 对于大一些的公司或项目，开发者的数量可能会是上千，每天都有成百上千次提交。 这很重要，因为随着开发者越来越多，在确保你的代码能干净地应用或轻松地合并时会遇到更多问题。 提交的改动可能表现为过时的，也可能在你正在做改动或者等待改动被批准应用时被合并入的工作严重损坏。 如何保证代码始终是最新的，并且提交始终是有效的？ 下一个影响因素是项目使用的工作流程。 它是中心化的吗，即每一个开发者都对主线代码有相同的写入权限？ 项目是否有一个检查所有补丁的维护者或整合者？ 是否所有的补丁是同行评审后批准的？ 你是否参与了那个过程？ 是否存在副官系统，你必须先将你的工作提交到上面？ 下一个影响因素是提交权限。 是否有项目的写权限会使向项目贡献所需的流程有极大的不同。 如果没有写权限，项目会选择何种方式接受贡献的工作？ 是否甚至有一个如何贡献的规范？ 你一次贡献多少工作？ 你多久贡献一次？ 所有这些问题都会影响实际如何向一个项目贡献，以及对你来说哪些工作流程更适合或者可用。 我们将会由浅入深，通过一系列用例来讲述其中的每一个方面；从这些例子应该能够建立实际中你需要的特定工作流程。 提交准则 在我们开始查看特定的用例前，这里有一个关于提交信息的快速说明。 有一个好的创建提交的准则并且坚持使用会让与 Git 工作和与其他人协作更容易。 Git 项目提供了一个文档，其中列举了关于创建提交到提交补丁的若干好的提示——可以在 Git 源代码中的 Documentation/SubmittingPatches 文件中阅读它。 首先，你的提交不应该包含任何空白错误。 Git 提供了一个简单的方式来检查这点——在提交前，运行 git diff --check ，它将会找到可能的空白错误并将它们为你列出来。 Figure 57. git diff --check 的输出 如果在提交前运行那个命令，可以知道提交中是否包含可能会使其他开发者恼怒的空白问题。 接下来，尝试让每一个提交成为一个逻辑上的独立变更集。 如果可以，尝试让改动可以理解——不要在整个周末编码解决五个问题，然后在周一时将它们提交为一个巨大的提交。 即使在周末期间你无法提交，在周一时使用暂存区域将你的工作最少拆分为每个问题一个提交，并且为每一个提交附带一个有用的信息。 如果其中一些改动修改了同一个文件，尝试使用 git add --patch 来部分暂存文件（在 交互式暂存 中有详细介绍）。 不管你做一个或五个提交，只要所有的改动都曾添加过，项目分支末端的快照就是一样的，所以尽量让你的开发者同事们在审查你的改动的时候更容易些吧。 当你之后需要时这个方法也会使拉出或还原一个变更集更容易些。 重写历史 描述了重写历史与交互式暂存文件的若干有用的 Git 技巧——在将工作发送给其他人前使用这些工具来帮助生成一个干净又易懂的历史。 最后一件要牢记的事是提交信息。 有一个创建优质提交信息的习惯会使 Git 的使用与协作容易的多。 一般情况下，信息应当以少于 50 个字符（25个汉字）的单行开始且简要地描述变更，接着是一个空白行，再接着是一个更详细的解释。 Git 项目要求一个更详细的解释，包括做改动的动机和它的实现与之前行为的对比——这是一个值得遵循的好规则。 使用指令式的语气来编写提交信息，比如使用“Fix bug”而非“Fixed bug”或“Fixes bug”。 这里是一份 最初由 Tim Pope 写的模板 ： 首字母大写的摘要（不多于 50 个字符） 如果必要的话，加入更详细的解释文字。在大概 72 个字符的时候换行。 在某些情形下，第一行被当作一封电子邮件的标题，剩下的文本作为正文。 分隔摘要与正文的空行是必须的（除非你完全省略正文）， 如果你将两者混在一起，那么在使用例如变基这样的工具时，它们会生成难以阅读的输出，让人困惑。 使用指令式的语气来编写提交信息：使用“Fix bug”而非“Fixed bug”或“Fixes bug”。 此约定与 git merge 和 git revert 命令生成提交说明相同。 空行接着更进一步的段落。 - 标号也是可以的。 - 项目符号可以使用典型的连字符或星号，后跟一个空格，行之间用空行隔开， 但是可以依据不同的惯例有所不同。 - 使用悬挂式缩进 如果你所有的提交信息都遵循此模版，那么对你和与你协作的其他开发者来说事情会变得非常容易。 Git 项目有一个良好格式化的提交信息——尝试在那儿运行 git log --no-merges 来看看漂亮的格式化的项目提交历史像什么样。 Note 按我们说的去做，不要照着我们做的去做。 为简单起见，本书中很多例子的提交说明并没有遵循这样良好的格式， 我们只是对 git commit 使用了 -m 选项。 简而言之，按我们说的去做，不要照着我们做的去做。 私有小型团队 你可能会遇到的最简单的配置是有一两个其他开发者的私有项目。 “私有” 在这个上下文中，意味着闭源——不可以从外面的世界中访问到。 你和其他的开发者都有仓库的推送权限。 在这个环境下，可以采用一个类似使用 Subversion 或其他集中式的系统时会使用的工作流程。 依然可以得到像离线提交、非常容易地新建分支与合并分支等高级功能，但是工作流程可以是很简单的；主要的区别是合并发生在客户端这边而不是在提交时发生在服务器那边。 让我们看看当两个开发者在一个共享仓库中一起工作时会是什么样子。 第一个开发者，John，克隆了仓库，做了改动，然后本地提交。 （为了缩短这些例子长度，协议信息已被替换为 … 。） # John's Machine $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'remove invalid default value' [master 738ee87] remove invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) 第二个开发者，Jessica，做了同样的事情——克隆仓库并提交了一个改动： # Jessica's Machine $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO $ git commit -am 'add reset task' [master fbff5bc] add reset task 1 files changed, 1 insertions(+), 0 deletions(-) 现在，Jessica 把她的工作推送到服务器上，一切正常： # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master 上方输出信息中最后一行显示的是推送操作执行完毕后返回的一条很有用的消息。 消息的基本格式是 <oldref>..<newref> fromref → toref ， oldref 的含义是推送前所指向的引用， newref 的含义是推送后所指向的引用， fromref 是将要被推送的本地引用的名字， toref 是将要被更新的远程引用的名字。 在后面的讨论中你还会看到类似的输出消息，所以对这条消息的含义有一些基础的了解将会帮助你理解仓库的诸多状态。 想要了解更多细节请访问文档 git-push 。 John 稍候也做了些改动，将它们提交到了本地仓库中，然后试着将它们推送到同一个服务器： # John's Machine $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' 这时 John 会推送失败，因为之前 Jessica 已经推送了她的更改。 如果之前习惯于用 Subversion 那么理解这点特别重要，因为你会注意到两个开发者并没有编辑同一个文件。 尽管 Subversion 会对编辑的不同文件在服务器上自动进行一次合并，但 Git 要求你先在本地合并提交。 换言之，John 必须先抓取 Jessica 的上游改动并将它们合并到自己的本地仓库中，才能被允许推送。 第一步，John 抓取 Jessica 的工作（这只会 抓取 Jessica 的上游工作，并不会将它合并到 John 的工作中）： $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master 在这个时候，John 的本地仓库看起来像这样： Figure 58. John 的分叉历史 现在 John 可以将抓取下来的 Jessica 的工作合并到他自己的本地工作中了： $ git merge origin/master Merge made by the 'recursive' strategy. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) 合并进行得很顺利——John 更新后的历史现在看起来像这样： Figure 59. 合并了 origin/master 之后 John 的仓库 此时，John 可能想要测试新的代码，以确保 Jessica 的工作没有影响他自己的工作， 当一切正常后，他就能将新合并的工作推送到服务器了： $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master 最终，John 的提交历史看起来像这样： Figure 60. 推送到 origin 服务器后 John 的历史 在此期间，Jessica 新建了一个名为 issue54 的主题分支，然后在该分支上提交了三次。 她还没有抓取 John 的改动，所以她的提交历史看起来像这样： Figure 61. Jessica 的主题分支 忽然，Jessica 发现 John 向服务器推送了一些新的工作，她想要看一下， 于是就抓取了所有服务器上的新内容： # Jessica's Machine $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master 那会同时拉取 John 推送的工作。 Jessica 的历史现在看起来像这样： Figure 62. 抓取 John 的改动后 Jessica 的历史 Jessica 认为她的主题分支已经准备好了，但她想知道需要将 John 工作的哪些合并到自己的工作中才能推送。 她运行 git log 找了出来： $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 remove invalid default value issue54..origin/master 语法是一个日志过滤器，要求 Git 只显示所有在后面分支 （在本例中是 origin/master ）但不在前面分支（在本例中是 issue54 ）的提交的列表。 我们将会在 提交区间 中详细介绍这个语法。 目前，我们可以从输出中看到有一个 John 生成的但是 Jessica 还没有合并的提交。 如果她合并 origin/master ，那个未合并的提交将会修改她的本地工作。 现在，Jessica 可以合并她的特性工作到她的 master 分支， 合并 John 的工作（ origin/master ）进入她的 master 分支，然后再次推送回服务器。 首先（在已经提交了所有 issue54 主题分支上的工作后），为了整合所有这些工作， 她切换回她的 master 分支。 $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Jessica 既可以先合并 origin/master 也可以先合并 issue54 ——它们都是上游，所以顺序并没有关系。 不论她选择的顺序是什么最终的结果快照是完全一样的；只是历史会稍微有些不同。 她选择先合并 issue54 ： $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) 没有发生问题，如你所见它是一次简单的快进合并。 现在 Jessica 在本地合并了之前抓取的 origin/master 分支上 John 的工作： $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) 每一个文件都干净地合并了，Jessica 的历史现在看起来像这样： Figure 63. 合并了 John 的改动后 Jessica 的历史 现在 origin/master 是可以从 Jessica 的 master 分支到达的， 所以她应该可以成功地推送（假设同一时间 John 并没有更多推送）： $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master 每一个开发者都提交了几次并成功地合并了其他人的工作。 Figure 64. 推送所有的改动回服务器后 Jessica 的历史 这是一个最简单的工作流程。 你通常会在一个主题分支上工作一会儿，当它准备好整合时就合并到你的 master 分支。 当想要共享工作时，如果有改动的话就抓取它然后合并到你自己的 master 分支， 之后推送到服务器上的 master 分支。通常顺序像这样： Figure 65. 一个简单的多人 Git 工作流程的通常事件顺序 私有管理团队 在接下来的场景中，你会看到大型私有团队中贡献者的角色。 你将学到如何在这种工作环境中工作，其中小组基于特性进行协作，而这些团队的贡献将会由其他人整合。 让我们假设 John 与 Jessica 在一个特性（ featureA ）上工作， 同时 Jessica 与第三个开发者 Josie 在第二个特性（ featureB ）上工作。 在本例中，公司使用了一种整合-管理者工作流程，独立小组的工作只能被特定的工程师整合， 主仓库的 master 分支只能被那些工程师更新。 在这种情况下，所有的工作都是在基于团队的分支上完成的并且稍后会被整合者拉到一起。 因为 Jessica 在两个特性上工作，并且平行地与两个不同的开发者协作，让我们跟随她的工作流程。 假设她已经克隆了仓库，首先决定在 featureA 上工作。 她为那个特性创建了一个新分支然后在那做了一些工作： # Jessica's Machine $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'add limit to log function' [featureA 3300904] add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) 在这个时候，她需要将工作共享给 John，所以她推送了 featureA 分支的提交到服务器上。 Jessica 没有 master 分支的推送权限——只有整合者有——所以为了与 John 协作必须推送另一个分支。 $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessica 向 John 发邮件告诉他已经推送了一些工作到 featureA 分支现在可以看一看。 当她等待 John 的反馈时，Jessica 决定与 Josie 开始在 featureB 上工作。 为了开始工作，她基于服务器的 master 分支开始了一个新分支。 # Jessica's Machine $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' 现在，Jessica 在 featureB 分支上创建了几次提交： $ vim lib/simplegit.rb $ git commit -am 'made the ls-tree function recursive' [featureB e5b0fdc] made the ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'add ls-files' [featureB 8512791] add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) 现在 Jessica 的仓库看起来像这样： Figure 66. Jessica 的初始提交历史 她准备好推送工作了，但是一封来自 Josie 的邮件告知一些初始的“featureB” 工作已经被推送到服务器的 featureBee 上了。 Jessica 在能够将她的工作推送到服务器前，需要将那些改动与她自己的合并。 她首先通过 git fetch 抓取了 Josie 的改动： $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee 假设 Jessica 还在她检出的 featureB 分支上，现在可以通过 git merge 将其合并到她做的工作中了： $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) 此时，Jessica 想要将所有合并后的“featureB”推送回服务器，但她并不想直接推送她自己的 featureB 分支。 由于 Josie 已经开启了一个上游的 featureBee 分支，因此 Jessica 想要推送到 这个 分支上，于是她这样做： $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee 这称作一个 引用规范 。 查看 引用规范 了解关于 Git 引用规范与通过它们可以做的不同的事情的详细讨论。 也要注意 -u 标记；这是 --set-upstream 的简写，该标记会为之后轻松地推送与拉取配置分支。 紧接着，John 发邮件给 Jessica 说他已经推送了一些改动到 featureA 分支并要求她去验证它们。 她运行一个 git fetch 来拉取下那些改动： $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Jessica 通过比较新抓取的 featureA 分支和她同一分支的本地副本，看到了 John 的新工作日志。 $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 changed log output to 30 from 25 如果 Jessica 觉得可以，她就能将 John 的新工作合并到她本地的 featureA 分支上： $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) 最后，Jessica 可能想要对整个合并后的内容做一些小修改， 于是她将这些修改提交到了本地的 featureA 分支，接着将最终的结果推送回了服务器。 $ git commit -am 'small tweak' [featureA 774b3ed] small tweak 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA Jessica 的提交历史现在看起来像这样： Figure 67. 在一个主题分支提交后 Jessica 的历史 这时，Jessica、Josie 与 John 通知整合者服务器上的 featureA 与 featureBee 分支准备好整合到主线中了。 在整合者将这些分支合并到主线后，就能一次将这个新的合并提交抓取下来，历史看起来就会像这样： Figure 68. 合并了 Jessica 的两个主题分支后她的历史 许多团队切换到 Git 就是看中了这种能让多个团队并行工作、并在之后合并不同工作的能力。 团队中更小一些的子小组可以通过远程分支协作而不必影响或妨碍整个团队的能力是 Git 的一个巨大优势。 在这儿看到的工作流程顺序类似这样： Figure 69. 这种管理团队工作流程的基本顺序 派生的公开项目 向公开项目做贡献有一点儿不同。 因为没有权限直接更新项目的分支，你必须用其他办法将工作给维护者。 第一个例子描述在支持简单派生的 Git 托管上使用派生来做贡献。 许多托管站点支持这个功能（包括 GitHub、BitBucket、repo.or.cz 等等），许多项目维护者期望这种风格的贡献。 下一节会讨论偏好通过邮件接受贡献补丁的项目。 首先，你可能想要克隆主仓库，为计划贡献的补丁或补丁序列创建一个主题分支，然后在那儿做工作。 顺序看起来基本像这样： $ git clone <url> $ cd project $ git checkout -b featureA ... work ... $ git commit ... work ... $ git commit Note 你可以用 rebase -i 将工作压缩成一个单独的提交，或者重排提交中的工作使补丁更容易被维护者审核—— 查看 重写历史 了解关于交互式变基的更多信息。 当你的分支工作完成后准备将其贡献回维护者，去原始项目中然后点击“Fork”按钮，创建一份自己的可写的项目派生仓库。 然后需要在本地仓库中将该仓库添加为一个新的远程仓库，在本例中称作 myfork ： $ git remote add myfork <url> 然后需要推送工作到上面。 相对于合并到主分支再推送上去，推送你正在工作的主题分支到仓库上更简单。 原因是工作如果不被接受或者是被拣选的，就不必回退你的 master 分支 （拣选操作 cherry-pick 详见 变基与拣选工作流 ）。 如果维护者合并、变基或拣选你的工作，不管怎样你最终会通过拉取他们的仓库找回来你的工作。 在任何情况下，你都可以使用下面的命令推送你的工作： $ git push -u myfork featureA 当工作已经被推送到你的派生仓库后，你需要通知原项目的维护者你有想要他们合并的工作。 这通常被称作一个 拉取请求（Pull Request） ，你通常可以通过网站生成它—— GitHub 有它自己的 Pull Request 机制，我们将会在 GitHub 介绍——也可以运行 git request-pull 命令然后将随后的输出通过电子邮件手动发送给项目维护者。 git request-pull 命令接受一个要拉取主题分支的基础分支，以及它们要拉取的 Git 仓库的 URL， 产生一个请求拉取的所有修改的摘要。 例如，Jessica 想要发送给 John 一个拉取请求，她已经在刚刚推送的分支上做了两次提交。她可以运行这个： $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: Jessica Smith (1): added a new function are available in the git repository at: git://githost/simplegit.git featureA Jessica Smith (2): add limit to log function change log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) 此输出可被发送给维护者——它告诉他们工作是从哪个分支开始的、提交的摘要、以及从哪里拉取这些工作。 在一个你不是维护者的项目上，通常有一个总是跟踪 origin/master 的 master 分支会很方便，在主题分支上做工作是因为如果它们被拒绝时你可以轻松地丢弃。 如果同一时间主仓库移动了然后你的提交不再能干净地应用，那么使工作主题独立于主题分支也会使你变基（rebase）工作时更容易。 例如，你想要提供第二个特性工作到项目，不要继续在刚刚推送的主题分支上工作——从主仓库的 master 分支重新开始： $ git checkout -b featureB origin/master ... work ... $ git commit $ git push myfork featureB $ git request-pull origin/master myfork ... email generated request pull to maintainer ... $ git fetch origin 现在，每一个特性都保存在一个贮藏库中——类似于补丁队列——可以重写、变基与修改而不会让特性互相干涉或互相依赖，像这样： Figure 70. featureB 的初始提交历史 假设项目维护者已经拉取了一串其他补丁，然后尝试拉取你的第一个分支，但是没有干净地合并。 在这种情况下，可以尝试变基那个分支到 origin/master 的顶部，为维护者解决冲突，然后重新提交你的改动： $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA 这样会重写你的历史，现在看起来像是 featureA 工作之后的提交历史 Figure 71. featureA 工作之后的提交历史 因为你将分支变基了，所以必须为推送命令指定 -f 选项，这样才能将服务器上有一个不是它的后代的提交的 featureA 分支替换掉。 一个替代的选项是推送这个新工作到服务器上的一个不同分支（可能称作 featureAv2 ）。 让我们看一个更有可能的情况：维护者看到了你的第二个分支上的工作并且很喜欢其中的概念，但是想要你修改一下实现的细节。 你也可以利用这次机会将工作基于项目现在的 master 分支。 你从现在的 origin/master 分支开始一个新分支，在那儿压缩 featureB 的改动，解决任何冲突，改变实现，然后推送它为一个新分支。 $ git checkout -b featureBv2 origin/master $ git merge --squash featureB ... change implementation ... $ git commit $ git push myfork featureBv2 --squash 选项接受被合并的分支上的所有工作，并将其压缩至一个变更集， 使仓库变成一个真正的合并发生的状态，而不会真的生成一个合并提交。 这意味着你的未来的提交将会只有一个父提交，并允许你引入另一个分支的所有改动， 然后在记录一个新提交前做更多的改动。同样 --no-commit 选项在默认合并过程中可以用来延迟生成合并提交。 现在你可以给维护者发送一条消息，表示你已经做了要求的修改然后他们可以在你的 featureBv2 分支上找到那些改动。 Figure 72. featureBv2 工作之后的提交历史 通过邮件的公开项目 许多项目建立了接受补丁的流程——需要检查每一个项目的特定规则，因为它们之间有区别。 因为有几个历史悠久的、大型的项目会通过一个开发者的邮件列表接受补丁，现在我们将会通过一个例子来演示。 工作流程与之前的用例是类似的——你为工作的每一个补丁序列创建主题分支。 区别是如何提交它们到项目中。 生成每一个提交序列的电子邮件版本然后邮寄它们到开发者邮件列表，而不是派生项目然后推送到你自己的可写版本。 $ git checkout -b topicA ... work ... $ git commit ... work ... $ git commit 现在有两个提交要发送到邮件列表。 使用 git format-patch 来生成可以邮寄到列表的 mbox 格式的文件——它将每一个提交转换为一封电子邮件，提交信息的第一行作为主题，剩余信息与提交引入的补丁作为正文。 它有一个好处是使用 format-patch 生成的一封电子邮件应用的提交正确地保留了所有的提交信息。 $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch format-patch 命令打印出它创建的补丁文件名字。 -M 开关告诉 Git 查找重命名。 文件最后看起来像这样： $ cat 0001-add-limit-to-log-function.patch From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001 From: Jessica Smith <jessica@example.com> Date: Sun, 6 Apr 2008 10:17:23 -0700 Subject: [PATCH 1/2] add limit to log function Limit log functionality to the first 20 --- lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/simplegit.rb b/lib/simplegit.rb index 76f47bc..f9815f1 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -14,7 +14,7 @@ class SimpleGit end def log(treeish = 'master') - command("git log #{treeish}") + command("git log -n 20 #{treeish}") end def ls_tree(treeish = 'master') -- 2.1.0 也可以编辑这些补丁文件为邮件列表添加更多不想要在提交信息中显示出来的信息。 如果在 --- 行与补丁开头（ diff --git 行）之间添加文本，那么开发者就可以阅读它，但是应用补丁时会忽略它。 为了将其邮寄到邮件列表，你既可以将文件粘贴进电子邮件客户端，也可以通过命令行程序发送它。 粘贴文本经常会发生格式化问题，特别是那些不会合适地保留换行符与其他空白的 “更聪明的” 客户端。 幸运的是，Git 提供了一个工具帮助你通过 IMAP 发送正确格式化的补丁，这可能对你更容易些。 我们将会演示如何通过 Gmail 发送一个补丁，它正好是我们所知最好的邮件代理；可以在之前提到的 Git 源代码中的 Documentation/SubmittingPatches 文件的最下面了解一系列邮件程序的详细指令。 首先，需要在 ~/.gitconfig 文件中设置 imap 区块。 可以通过一系列的 git config 命令来分别设置每一个值，或者手动添加它们，不管怎样最后配置文件应该看起来像这样： [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = YX]8g76G_2^sFbd port = 993 sslverify = false 如果 IMAP 服务器不使用 SSL，最后两行可能没有必要，host 的值会是 imap:// 而不是 imaps:// 。 当那些设置完成后，可以使用 git imap-send 将补丁序列放在特定 IMAP 服务器的 Drafts 文件夹中： $ cat *.patch |git imap-send Resolving imap.gmail.com... ok Connecting to [74.125.142.109]:993... ok Logging in... sending 2 messages 100% (2/2) done 此时，你可以到 Drafts 文件夹中，修改收件人字段为想要发送补丁的邮件列表， 可能需要抄送给维护者或负责那个部分的人，然后发送。 你也可以通过一个 SMTP 服务器发送补丁。 同之前一样，你可以通过一系列的 git config 命令来分别设置选项， 或者你可以手动地将它们添加到你的 ~/.gitconfig 文件的 sendmail 区块： [sendemail] smtpencryption = tls smtpserver = smtp.gmail.com smtpuser = user@gmail.com smtpserverport = 587 当这完成后，你可以使用 git send-email 发送你的补丁： $ git send-email *.patch 0001-added-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch Who should the emails appear to be from? [Jessica Smith <jessica@example.com>] Emails will be sent from: Jessica Smith <jessica@example.com> Who should the emails be sent to? jessica@example.com Message-ID to be used as In-Reply-To for the first email? y 然后，对于正在发送的每一个补丁，Git 会吐出这样的一串日志信息： (mbox) Adding cc: Jessica Smith <jessica@example.com> from \line 'From: Jessica Smith <jessica@example.com>' OK. Log says: Sendmail: /usr/sbin/sendmail -i jessica@example.com From: Jessica Smith <jessica@example.com> To: jessica@example.com Subject: [PATCH 1/2] added limit to log function Date: Sat, 30 May 2009 13:29:15 -0700 Message-Id: <1243715356-61726-1-git-send-email-jessica@example.com> X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty In-Reply-To: <y> References: <y> Result: OK 总结 这个部分介绍了处理可能会遇到的几个迥然不同类型的 Git 项目的一些常见的工作流程， 介绍了帮助管理这个过程的一些新工具。 接下来，你会了解到如何在贡献的另一面工作：维护一个 Git 项目。 你将会学习如何成为一个仁慈的独裁者或整合管理者。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://www.facebook.com/r.php?api_key=860047027665875&app_id=860047027665875&cancel_url=https%3A%2F%2F10web.io%2Fblog%2Fvps-hosting-vs-dedicated-hosting%2F&next=https%3A%2F%2Fwww.facebook.com%2Fdialog%2Fsend%3F_path%3Dsend%26app_id%3D860047027665875%26client_id%3D860047027665875%26redirect_uri%3Dhttps%253A%252F%252F10web.io%252Fblog%252Fvps-hosting-vs-dedicated-hosting%252F%26display%3Dpage%26link%3Dhttps%253A%252F%252F10web.io%252Fblog%252Fvps-hosting-vs-dedicated-hosting%252F%26from_login%3D1&locale=ko_KR&display=page&entry_point=login | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 가입하기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:41 |
https://git-scm.com/book/fr/v2/Les-bases-de-Git-Annuler-des-actions | Git - Annuler des actions About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Démarrage rapide 1.1 À propos de la gestion de version 1.2 Une rapide histoire de Git 1.3 Rudiments de Git 1.4 La ligne de commande 1.5 Installation de Git 1.6 Paramétrage à la première utilisation de Git 1.7 Obtenir de l’aide 1.8 Résumé 2. Les bases de Git 2.1 Démarrer un dépôt Git 2.2 Enregistrer des modifications dans le dépôt 2.3 Visualiser l’historique des validations 2.4 Annuler des actions 2.5 Travailler avec des dépôts distants 2.6 Étiquetage 2.7 Les alias Git 2.8 Résumé 3. Les branches avec Git 3.1 Les branches en bref 3.2 Branches et fusions : les bases 3.3 Gestion des branches 3.4 Travailler avec les branches 3.5 Branches de suivi à distance 3.6 Rebaser (Rebasing) 3.7 Résumé 4. Git sur le serveur 4.1 Protocoles 4.2 Installation de Git sur un serveur 4.3 Génération des clés publiques SSH 4.4 Mise en place du serveur 4.5 Démon (Daemon) Git 4.6 HTTP intelligent 4.7 GitWeb 4.8 GitLab 4.9 Git hébergé 4.10 Résumé 5. Git distribué 5.1 Développements distribués 5.2 Contribution à un projet 5.3 Maintenance d’un projet 5.4 Résumé 6. GitHub 6.1 Configuration et paramétrage d’un compte 6.2 Contribution à un projet 6.3 Maintenance d’un projet 6.4 Gestion d’un regroupement 6.5 Écriture de scripts pour GitHub 6.6 Résumé 7. Utilitaires Git 7.1 Sélection des versions 7.2 Indexation interactive 7.3 Remisage et nettoyage 7.4 Signer votre travail 7.5 Recherche 7.6 Réécrire l’historique 7.7 Reset démystifié 7.8 Fusion avancée 7.9 Rerere 7.10 Déboguer avec Git 7.11 Sous-modules 7.12 Empaquetage (bundling) 7.13 Replace 7.14 Stockage des identifiants 7.15 Résumé 8. Personnalisation de Git 8.1 Configuration de Git 8.2 Attributs Git 8.3 Crochets Git 8.4 Exemple de politique gérée par Git 8.5 Résumé 9. Git et les autres systèmes 9.1 Git comme client 9.2 Migration vers Git 9.3 Résumé 10. Les tripes de Git 10.1 Plomberie et porcelaine 10.2 Les objets de Git 10.3 Références Git 10.4 Fichiers groupés 10.5 La refspec 10.6 Les protocoles de transfert 10.7 Maintenance et récupération de données 10.8 Les variables d’environnement 10.9 Résumé A1. Annexe A: Git dans d’autres environnements A1.1 Interfaces graphiques A1.2 Git dans Visual Studio A1.3 Git dans Visual Studio Code A1.4 Git dans IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git dans Sublime Text A1.6 Git dans Bash A1.7 Git dans Zsh A1.8 Git dans PowerShell A1.9 Résumé A2. Annexe B: Embarquer Git dans vos applications A2.1 Git en ligne de commande A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Commandes Git A3.1 Installation et configuration A3.2 Obtention et création des projets A3.3 Capture d’instantané basique A3.4 Création de branches et fusion A3.5 Partage et mise à jour de projets A3.6 Inspection et comparaison A3.7 Débogage A3.8 Patchs A3.9 Courriel A3.10 Systèmes externes A3.11 Administration A3.12 Commandes de plomberie 2nd Edition 2.4 Les bases de Git - Annuler des actions Annuler des actions À tout moment, vous pouvez désirer annuler une de vos dernières actions. Dans cette section, nous allons passer en revue quelques outils de base permettant d’annuler des modifications. Il faut être très attentif car certaines de ces annulations sont définitives (elles ne peuvent pas être elles-mêmes annulées). C’est donc un des rares cas d’utilisation de Git où des erreurs de manipulation peuvent entraîner des pertes définitives de données. Une des annulations les plus communes apparaît lorsqu’on valide une modification trop tôt en oubliant d’ajouter certains fichiers, ou si on se trompe dans le message de validation. Si vous souhaitez rectifier cette erreur, vous pouvez valider le complément de modification avec l’option --amend : $ git commit --amend Cette commande prend en compte la zone d’index et l’utilise pour le commit . Si aucune modification n’a été réalisée depuis la dernière validation (par exemple en lançant cette commande immédiatement après la dernière validation), alors l’instantané sera identique et la seule modification à introduire sera le message de validation. L’éditeur de message de validation démarre, mais il contient déjà le message de la validation précédente. Vous pouvez éditer ce message normalement, mais il écrasera le message de la validation précédente. Par exemple, si vous validez une version puis réalisez que vous avez oublié d’indexer les modifications d’un fichier que vous vouliez ajouter à ce commit , vous pouvez faire quelque chose comme ceci : $ git commit -m 'validation initiale' $ git add fichier_oublie $ git commit --amend Vous n’aurez au final qu’un unique commit — la seconde validation remplace le résultat de la première. Note Il est important de comprendre que lorsque vous être en train de modifier votre dernier commit, vous n’êtes pas vraiment en train de le réparer, mais plutôt de le remplacer complètement par un commit nouveau, amélioré qui écarte l’ancien commit et vient à sa place. Dans les faits, c’est comme si l’ancien commit n’avait jamais eu lieu, et il n’apparaîtra plus dans l’historique de votre dépôt. L’intérêt immédiat de la rectification de commit est de faire des petites améliorations de votre dernier commit, sans encombrer l’historique de votre dépôt avec des messages de validations de la forme « Oups, j’avais oublié ce fichier » ou « Zut, correction d’une faute sur le dernier commit ». Note Ne rectifiez que les commits qui ne sont que locaux et n’ont pas été poussés. La rectification de commit qui ont été poussés et la poussée en force de branche risque de créer des problèmes avec vos collaborateurs. Pour plus d’information sur ce qui arrive si vous le faites et comment s’en sortir en fin de compte, lisez Les dangers du rebasage Désindexer un fichier déjà indexé Les deux sections suivantes démontrent comment bricoler les modifications dans votre zone d’index et votre zone de travail. Un point sympathique est que la commande permettant de connaître l’état de ces deux zones vous rappelle aussi comment annuler les modifications. Par exemple, supposons que vous avez modifié deux fichiers et voulez les valider comme deux modifications indépendantes, mais que vous avez tapé accidentellement git add * et donc indexé les deux. Comment annuler l’indexation d’un des fichiers ? La commande git status vous le rappelle : $ git add . $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) renommé : README.md -> README modifié : CONTRIBUTING.md Juste sous le texte « Modifications qui seront validées », elle vous indique d’utiliser git reset HEAD <fichier>… pour désindexer un fichier. Utilisons donc ce conseil pour désindexer le fichier CONTRIBUTING.md : $ git reset HEAD CONTRIBUTING.md Modifications non indexées après reset : M CONTRIBUTING.md $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) renommé : README.md -> README Modifications qui ne seront pas validées : (utilisez "git add <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git checkout -- <fichier>..." pour annuler les modifications dans la copie de travail) modifié : CONTRIBUTING.md La commande à taper peut sembler étrange mais elle fonctionne. Le fichier CONTRIBUTING.md est modifié mais de retour à l’état non indexé. Note git reset peut être une commande dangereuse, surtout conjuguée avec l’option --hard . Cependant, dans le cas présent, le fichier dans la copie de travail n’a pas été touché, donc c’est relativement bénin. Pour l’instant, cette invocation magique est la seule à connaître pour la commande git reset . Nous entrerons plus en détail sur ce que reset réalise et comment le maîtriser pour faire des choses intéressantes dans Reset démystifié Réinitialiser un fichier modifié Que faire si vous réalisez que vous ne souhaitez pas conserver les modifications du fichier CONTRIBUTING.md ? Comment le réinitialiser facilement, le ramener à son état du dernier instantané (ou lors du clonage, ou dans l’état dans lequel vous l’avez obtenu dans votre copie de travail) ? Heureusement, git status vous indique comment procéder. Dans le résultat de la dernière commande, la zone de travail ressemble à ceci : Modifications qui ne seront pas validées : (utilisez "git add <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git checkout -- <fichier>..." pour annuler les modifications dans la copie de travail) modifié : CONTRIBUTING.md Ce qui vous indique de façon explicite comment annuler des modifications que vous avez faites. Faisons comme indiqué : $ git checkout -- CONTRIBUTING.md $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) renommé : README.md -> README Vous pouvez constater que les modifications ont été annulées. Important Vous devriez aussi vous apercevoir que c’est une commande dangereuse : toutes les modifications que vous auriez réalisées sur ce fichier ont disparu — vous venez tout juste de l’écraser avec un autre fichier. N’utilisez jamais cette commande à moins d’être vraiment sûr de ne pas vouloir de ces modifications. Si vous souhaitez seulement écarter momentanément cette modification, nous verrons comment mettre de côté et créer des branches dans le chapitre Les branches avec Git ; ce sont de meilleures façons de procéder. Souvenez-vous, tout ce qui a été validé dans Git peut quasiment toujours être récupéré. Y compris des commits sur des branches qui ont été effacées ou des commits qui ont été écrasés par une validation avec l’option --amend (se référer au chapitre Récupération de données pour la récupération de données). Cependant, tout ce que vous perdez avant de l’avoir validé n’a aucune chance d’être récupérable via Git. Réinitialiser les choses avec git restore Git version 2.25.0 a introduit une nouvelle commande : git restore . C’est fondamentalement une alternative à git reset que nous venons de traiter. Depuis Git version 2.25.0, Git utilisera git restore au lieu de git reset pour beaucoup d’opérations de réinitialisation. Retraçons nos pas, et réinitialisons les choses avec git restore au lieu de git reset . Désindexer un fichier indexé avec git restore Les deux sections suivantes démontrent comment travailler avec votre zone d’index et votre répertoire de travail au moyen de git restore . Le point positif est que la commande que vous utilisez pour déterminer l’état de ces deux zones vous rappelle comment réinitialiser les modifications qui s’y appliquent. Par exemple, disons que vous avez modifié deux fichiers et que vous souhaitez les valider comme deux modifications distinctes, mais que vous avez accidentellement tapé git add * et avez indexé les deux. Comment désindexer l’une de deux ? la commande git status vous le rappelle : $ git add * $ git status Sur la branche master Modifications qui seront validées : (utilisez "git restore --staged <fichier>..." pour désindexer) modifié : CONTRIBUTING.md renommé : README.md -> README Juste en dessous du texte “Modifications qui seront validées”, il nous indique d’utiliser git restore --staged <fichier>… pour désindexer. Utilisons ce conseil pour désindexer le fichier CONTRIBUTING.md . $ git restore --staged CONTRIBUTING.md $ git status Sur la branche master Modifications qui seront validées : (utilisez "git restore --staged <fichier>..." pour désindexer) renommé : README.md -> README Modifications qui ne seront pas validées : (utilisez "git add/rm <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git restore <fichier>..." pour annuler les modifications dans le répertoire de travail) modifié : CONTRIBUTING.md Le fichier CONTRIBUTING.md est modifié mais une fois de plus non-indexé. Réinitialiser un fichier modifié avec git restore Que faire si vous vous apercevez que vous ne voulez pas garder les modifications du fichier CONTRIBUTING.md ? Comment le modifier simplement — le réinitialiser à l’état qu’il avait lors de votre dernier commit (ou lors du clonage ou de toute manière où il apparaissait dans le dépôt) ? Heureusement, git status indique aussi comment faire. Dans la sortie du dernier exemple, la zone non-indexée ressemblait à ceci : Modifications qui ne seront pas validées : (utilisez "git add/rm <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git restore <fichier>..." pour annuler les modifications dans le répertoire de travail) modifié : CONTRIBUTING.md Cela vous indique assez explicitement comment laisser les modifications que vous avez faites. Faisons comme indiqué : $ git restore CONTRIBUTING.md $ git status Sur la branche master Modifications qui seront validées : (utilisez "git restore --staged <fichier>..." pour désindexer) renommé : README.md -> README Important Il faut bien comprendre que git restore <fichier> est une commande dangereuse. Toute modification locale à ce fichier va être perdue — Git remplace ce fichier par la version la plus récemment validée. N’utilisez pas cette commande à moins d’être absolument certain de ne pas vouloir de ces modifications locales. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://support.smartbear.com/reflect/docs/en/integrations.html#in-this-section-2110472 | Integrations | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Integrations Integrations Learn how to integrate Reflect into your existing development and/or testing workflows. In This Section Email Notifications Get automated alerts when tests start failing. Issue Trackers Create bug tickets for failing tests directly from Reflect. Continuous Integration (CI/CD) Automatically execute Reflect tests from within your Continuous Integration/Continuous Deployment pipeline. Slack Send automatic notifications to a Slack channel of your choice when tests fail. GitHub Connect to GitHub to allow Reflect to run tests on every Pull Request and mark PRs as passing/failing. Test Case Management Automatically sync Reflect tests and test results to your existing Test Case Management tool In this section : Integrations In This Section Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:41 |
https://huggingface.co/ahmedsqrd/activity/community | ahmedsqrd (Ahmed Ahmed) – Community Activity Hugging Face Models Datasets Spaces Community Docs Enterprise Pricing Log In Sign Up 3 1 Ahmed Ahmed ahmedsqrd Follow eliebak's profile picture 21world's profile picture yjernite's profile picture 5 followers · 2 following AI & ML interests None yet Organizations ahmedsqrd 's activity All Models Datasets Spaces Papers Collections Community Posts Upvotes Likes Articles New activity in allenai/OLMo-7B-0424-hf over 1 year ago Discrepancy between tokenizer and vocab 4 #5 opened over 1 year ago by ahmedsqrd No revisions.txt file 3 #3 opened over 1 year ago by ahmedsqrd New activity in allenai/OLMo-7B-hf over 1 year ago Intermediate checkpoints for HF model 2 #1 opened over 1 year ago by przvl System theme Company TOS Privacy About Careers Website Models Datasets Spaces Pricing Docs | 2026-01-13T09:29:41 |
https://support.microsoft.com/nb-no/office/hva-er-skift-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | Hva er skift? - Støtte for Microsoft Relaterte emner × Microsoft Teams-videoopplæring Hurtigstart for Microsoft Teams Hva er Microsoft Teams? Logge på og komme i gang Chatte og dele filer Samarbeide Finn ut mer Introduksjon til Microsoft Teams Komme i gang med Microsoft Teams Komme i gang med Chat Kom i gang med møter Kom i gang med apper Konfigurere og tilpasse teamet ditt Opprette et team med maler Jobb med eksterne gjester Administrere teaminnstillinger Samarbeide i team og kanaler Tips: Sende en e-postmelding til en kanal Opprette en plan med Planner Arbeide med innlegg og meldinger Publiser en melding til flere kanaler Søk etter og finn filer Laste opp og dele filer Søk etter og filtrer personer og filer Søke og filtrere meldinger Tips for Teams-filer Starte chatter og samtaler Oversikt over Teams-samtaler Ringe Tips for Teams-samtaler Skjul chatter og slett meldinger Utnevn en representant til å svare for deg Administrere møter Bli med i et Teams-møte Tips for Teams-møter Møt umiddelbart Administrere møter Planlegge et nettseminar Vis skjermen i et møte Konfigurere og delta i direktesendte arrangementer Planlegge et direktesendt arrangement Produsere et direktesendt arrangement Bli med i et direktesendt arrangement Moderere spørsmål og svar Utforske apper og verktøy Finn og bruk apper Administrer teamtidsplaner med Skift Hva er Skift? Lag en Skiftplan Administrer en skiftplan Opprette godkjenninger Hva er Godkjenninger? Opprett en godkjenning Opprett en godkjenning fra en chat Opprette en e-signeringsgodkjenning Oppdage maler i Godkjenninger Opprett godkjenninger med maler Opprett maler gjennom hele organisasjonen Virtuelle avtaler i Microsoft Bookings Hva er virtuelle avtaler? Send SMS-varsler til eksterne gjester Utfør en avtale Lagre en avtale Administrere aktivitetsfeeden Administrere varselinnstillinger Teams på farten Start en chat på farten Opprette en kanal mens du er på farten Bli med i et møte på farten Aktivitetsfeed på farten Gå til hovedinnhold Microsoft Støtte Støtte Støtte Hjem Microsoft 365 Office Teams-støtte Emner Møter Chat Varsler og innstillinger Teams og kanaler Anrop og enheter Filer Apper og tjenester Hurtigveiledning Chat Gruppechat Varsler Teams Kanaler Samtaler Filer Apper Loop-komponenter Nyheter Ressurser Videoopplæring Feilsøke Her i Teams Tilgjengelighet Teams-funksjoner etter plattform Microsoft Teams (gratis) Fellesskapsforum Blogg for det tekniske felleskapet Instruktørledet opplæring For administratorer og IT-eksperter For Utdanning Mer Kjøp Microsoft 365 Alt fra Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Spesialtilbud Liten bedrift Kundestøtte Programvare Programvare Windows-apper AI OneDrive Outlook Overgang fra Skype til Teams OneNote Microsoft Teams PCer og enheter PCer og enheter Kjøp Xbox Tilbehør Underholdning Underholdning Xbox Game Pass Ultimate Xbox og spill PC-spill Bedrift Bedrift Microsoft Sikkerhet Azure Dynamics 365 Microsoft 365 for bedrifter Microsoft Industry Microsoft Power Platform Windows 365 Utvikler og IT Utvikler og IT Microsoft Developer Microsoft Learn Støtte for KI-apper på markedsplassen Microsoft Tech-fellesskap Microsoft Marketplace Visual Studio Marketplace Rewards Annen Annen Microsoft Rewards Gratis nedlastinger og sikkerhet Utdanning Gavekort Lisensiering Vis områdekart Søk Søk etter hjelp Ingen resultater Avbryt Logg på Logg på med Microsoft Logg på, eller opprett en konto. Hei, Velg en annen konto. Du har flere kontoer Velg kontoen du vil logge på med. Relaterte emner Microsoft Teams-videoopplæring Hurtigstart for Microsoft Teams Hva er Microsoft Teams? Logge på og komme i gang Chatte og dele filer Samarbeide Finn ut mer Introduksjon til Microsoft Teams Komme i gang med Microsoft Teams Komme i gang med Chat Kom i gang med møter Kom i gang med apper Konfigurere og tilpasse teamet ditt Opprette et team med maler Jobb med eksterne gjester Administrere teaminnstillinger Samarbeide i team og kanaler Tips: Sende en e-postmelding til en kanal Opprette en plan med Planner Arbeide med innlegg og meldinger Publiser en melding til flere kanaler Søk etter og finn filer Laste opp og dele filer Søk etter og filtrer personer og filer Søke og filtrere meldinger Tips for Teams-filer Starte chatter og samtaler Oversikt over Teams-samtaler Ringe Tips for Teams-samtaler Skjul chatter og slett meldinger Utnevn en representant til å svare for deg Administrere møter Bli med i et Teams-møte Tips for Teams-møter Møt umiddelbart Administrere møter Planlegge et nettseminar Vis skjermen i et møte Konfigurere og delta i direktesendte arrangementer Planlegge et direktesendt arrangement Produsere et direktesendt arrangement Bli med i et direktesendt arrangement Moderere spørsmål og svar Utforske apper og verktøy Finn og bruk apper Administrer teamtidsplaner med Skift Hva er Skift? Lag en Skiftplan Administrer en skiftplan Opprette godkjenninger Hva er Godkjenninger? Opprett en godkjenning Opprett en godkjenning fra en chat Opprette en e-signeringsgodkjenning Oppdage maler i Godkjenninger Opprett godkjenninger med maler Opprett maler gjennom hele organisasjonen Virtuelle avtaler i Microsoft Bookings Hva er virtuelle avtaler? Send SMS-varsler til eksterne gjester Utfør en avtale Lagre en avtale Administrere aktivitetsfeeden Administrere varselinnstillinger Teams på farten Start en chat på farten Opprette en kanal mens du er på farten Bli med i et møte på farten Aktivitetsfeed på farten Hva er skift? Gjelder for Teams Microsoft Teams Prøv det! Skift-appen i Microsoft Teams er et verktøy for administrasjon av tidsplaner og tidssporing som hjelper deg med å opprette, oppdatere og administrere tidsplaner for teamet. Tidsplaner – Opprett, rediger og administrer en tidsplan for teamet. En skiftplan viser dager øverst, gruppemedlemmer vises til venstre og tildelte skift vises i kalenderen. Tidsplaninnstillinger – Definer tidsplanalternativene i Skift-innstillingene, og velg skiftfunksjonene du vil gjøre tilgjengelig for teamet. Grupper – Legg til tidsplangrupper for å organisere gruppemedlemmer i tidsplanen etter jobbtype eller plassering. Skift – Tilordne skift til gruppemedlemmer. Opprett et skift fra grunnen av, eller kopier et eksisterende skift. Åpne skift – Hver gruppe i tidsplanen har en Åpen skift-rad . Legg til åpne skift i tidsplanen som alle kan be om. Tidsklokke – Aktiver tidsklokken i Skift-innstillingene for å la teamet stemple inn og ut av skift. Forespørsler – se gjennom og svar på forespørsler om fri, åpne skift, skiftbytte og tilbud. Merker – Bruk skiftbaserte koder til raskt å kommunisere med alle som for øyeblikket er på skift. Publiser tidsplanen – Når du er ferdig med å gjøre endringer i tidsplanen, kan du dele den med teamet slik at alle er oppdatert. Vil du vite mer? Komme i gang med Skift Opprette en gruppeplan i Skift Legge til skift i tidsplanen i Skift Publiser en tidsplan i Skift Behandle skiftforespørsler og fri i Skift Slå på skiftbaserte koder i Teams ABONNER PÅ RSS-FEEDER Trenger du mer hjelp? Vil du ha flere alternativer? Oppdag Community Utforsk abonnementsfordeler, bla gjennom opplæringskurs, finn ut hvordan du sikrer enheten og mer. Abonnementsfordeler for Microsoft 365 Microsoft 365-opplæring Microsoft Sikkerhet Tilgjengelighetssenter Fellesskap hjelper deg med å stille og svare på spørsmål, gi tilbakemelding og høre fra eksperter med stor kunnskap. Spør Microsoft-fellesskapet Teknisk fellesskap for Microsoft Windows Insider-medlemmer Microsoft 365 Insiders Var denne informasjonen nyttig? Ja Nei Takk! Har du flere tilbakemeldinger til Microsoft? Kan du hjelpe oss med å bli bedre? (Send tilbakemelding til Microsoft, slik at vi kan hjelpe deg.) Hvor fornøyd er du med språkkvaliteten? Hva påvirket opplevelsen din? Løste problemet mitt Tydelige instruksjoner Enkelt å følge Ingen sjargong Bilder hjalp Oversettelseskvalitet Samsvarte ikke med skjermen min Feil instruksjoner For teknisk Ikke nok informasjon Ikke nok bilder Oversettelseskvalitet Har du ytterligere tilbakemeldinger? (Valgfritt) Send tilbakemelding Når du trykker på Send inn, blir tilbakemeldingen brukt til å forbedre Microsoft-produkter og -tjenester. IT-administratoren kan samle inn disse dataene. Personvernerklæring. Takk for tilbakemeldingen! × Nyheter Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot for organisasjoner Copilot til personlig bruk Microsoft 365 Utforsk Microsoft-produkter Windows 11-apper Microsoft Store Kontoprofil Nedlastingssenter Kundestøtte for Microsoft Store Returer Ordresporing Gjenvinning Kommersielle garantier Utdanning Microsoft Education Enheter for utdanning Microsoft Teams for utdanning Microsoft 365 Education Office Education Lærerutdanning og -utvikling Tilbud for elever og foreldre Azure for students Bedrift Microsoft Sikkerhet Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Liten bedrift Utvikler og IT Microsoft Developer Microsoft Learn Støtte for KI-apper på markedsplassen Microsoft Tech-fellesskap Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Selskap Karriere Om Microsoft Microsoft og personvern Investorer Bærekraft Norsk bokmål (Norge) Ikon for å velge bort personvernvalg Dine personvernvalg Ikon for å velge bort personvernvalg Dine personvernvalg Personvern for forbrukerhelse Kontakt Microsoft Personvern Behandle informasjonskapsler Vilkår for bruk Varemerker Om annonsene © Microsoft 2026 | 2026-01-13T09:29:41 |
https://www.microsoft.com/ko-kr/ai/financial-services | Microsoft for Financial Services | Microsoft AI This is the Trace Id: 72cb174770df28dd95752a4c18c7303c 주 콘텐츠로 건너뛰기 Microsoft Microsoft AI Microsoft AI Microsoft AI 홈 제품 및 솔루션 조직용 조직용 Microsoft 365 Copilot Microsoft 365 Copilot 앱 다운로드 조직용 Copilot Agent 365 Customize your Copilot Customize your Copilot Copilot Studio Build your own Build your own Microsoft Foundry Foundry Tools Azure AI 솔루션 파트너 제공 파트너 제공 Microsoft Marketplace Intelligent PCs Intelligent PCs Copilot+ PCs 개인용 개인용 Microsoft Copilot Copilot 앱 다운로드 업계 솔루션 소비재 보안 및 인텔리전스 교육 에너지 및 자원 에너지 및 자원 개요 전력 및 유틸리티 석유 및 가스 채광 금융 서비스 금융 서비스 개요 뱅킹 자본 시장 보험 정부 기관 정부 기관 개요 대중교통 및 도시 인프라 공공 금융 공중 보건 및 복지 서비스 공공 안전 및 정의 의료 서비스 및 생명 과학 의료 서비스 및 생명 과학 개요 공급자 Payors 생명과학 제조 제조 개요 산업 혁신 미디어 및 엔터테인먼트 이동성 이동성 개요 자동차 여행 및 교통 소매 통신 비즈니스 리더를 위한 AI AI 사용 사례 신뢰할 수 있는 AI 책임 있는 AI 책임 있는 AI Microsoft 책임 있는 AI 원칙 및 접근 방식 도구 및 사용 지속 가능성 지속 가능성 지속 가능성 강화 보안 유지 보안 유지 AI 보안 강화 데이터 보호 및 개인 정보 알아보기 AI 101 AI 학습 허브 업계 블로그 Microsoft Cloud 블로그 지원 비즈니스 고객을 위한 지원 산업 문서 자세히 DORA 규정 준수를 안내하고 운영 복원력을 강화하세요. 전자책 읽기 산업 Microsoft for Financial Services</h1> "> 금융 서비스용 Microsoft AI 시대에 비즈니스 가치를 가속화하고 고객 관계를 더욱 깊게 만드세요. 자세한 정보 비디오 보기 개요 개요 산업 솔루션 고객 스토리 파트너 추천 앱 제품 리소스 개요 Lead through&nbsp;AI&nbsp;innovation</h2> "> AI 혁신을 선도하세요 금융 서비스를 위한 클라우드와 AI 솔루션으로 데이터, 자동화, 인텔리전스를 최대한 활용하세요. 금융 서비스 환경 혁신 심층적인 인사이트와 관계를 통해 차별화된 고객 및 클라이언트 환경을 제공합니다. 금융 서비스 직원 역량 강화 최신 AI 혁신으로 개인, 팀, 조직의 생산성을 향상하세요. 위험 및 규정 준수 관리 위험 인사이트를 강화하고, 규정 준수를 용이하게 하고, 금융 범죄를 방지합니다. 핵심 시스템 현대화 핵심 시스템과 데이터를 클라우드로 가져와서 새로운 고객의 요구를 충족하고 비용을 절감하세요. 산업 솔루션 Explore solutions by industry</h2> "> 산업별 솔루션 살펴보기 은행, 보험, 자본 시장을 위한 클라우드 및 AI 기반 솔루션에 대해 알아보세요. 뱅킹 고유한 고객 환경을 제공하고 새롭고 혁신적인 작업 방식을 정의합니다. 자세한 정보 보험 고객 환경을 혁신하고, 생산성을 높이고, 위험을 관리하고, 운영을 현대화합니다. 자세한 정보 자본 시장 안전하고 규정을 준수하는 클라우드 기반 솔루션으로 가치 창출을 촉진하고 협업을 향상하세요. 자세한 정보 보안 및 규정 준수 Build on a trusted cloud</h2> "> 신뢰할 수 있는 클라우드에 구축 인텔리전스, 보안, 규정 준수를 기반으로 리스크를 완화하고 비즈니스 가치를 창출하세요. 다음을 수행할 수 있습니다. 규정 준수 요구 사항을 충족합니다. 보안 및 개인 정보 보호 강화 복원력 및 투명성을 강화합니다. 자세한 정보 고객 스토리 See how organizations innovate with AI</h2> "> 조직이 AI로 혁신하는 방법을 확인하세요 이전 슬라이드 다음 슬라이드 “[Azure AI 검색]의 성능은 Microsoft와 협력한 결정이 옳았다는 확신을 더욱 강화해줍니다.” Ilias Fotopoulos, 수석 AI 엔지니어, UBS 26M 검색 가능한 문서 제품 파운드리 모델에서의 Azure OpenAI Azure AI 검색 스토리 읽기 “우리는 비즈니스 영향, 고객 경험, 올바른 기술이 만나는 지점에서 마법이 일어난다고 믿습니다.” Sathish Muthukrishnan, 최고정보·데이터·디지털 책임자, Ally Financial >10,000 통화가 실시간으로 요약됩니다 제품 Foundry Models에서의 Azure OpenAI Microsoft Foundry 스토리 읽기 “[Microsoft 365 Copilot]을 기반으로 모든 서비스에 AI 기능이 더 깊이 통합될 것으로 기대합니다.” Mark Eramo, 공동대표, S&P Global Commodity Insights 95% 더 빠른 데이터 추출 98% 더 빠른 비교 분석 제품 Microsoft Copilot Microsoft 365 스토리 읽기 “AI 솔루션 작업을 위해 Microsoft를 선택한 이유는 AI에 대한 Microsoft의 전문 지식 때문이었습니다.” Sheridan Folger, 디지털 서비스 및 인지 AI 매니저, John Hancock 종일 제공된 AI 증강 서비스 제품 Foundry Tools Azure AI Bot Service 사례 읽기 “필요한 경우 지점 직원은 Azure OpenAI 기반 챗봇을 사용하여 모든 고객 상호 작용에서 시간을 절약합니다.” Gizem Yalçın, 스마트 디지털 어시스턴트 애플리케이션 제품 책임자, Akbank 10,000 쿼리된 문서 90% 챗봇 응답 정확도 제품 Azure Foundry Models에서의 Azure OpenAI 사례 읽기 “Dynamics 365를 사용하여 프로세스를 최적화하고 대량 전자 메일 노이즈를 크게 줄일 수 있었습니다.” Shaelyn Otikor-Miller, SVP, 글로벌 디지털 워크플레이스 책임자, Northern Trust 67% 사례 볼륨 감소 제품 Dynamics 365 Customer Service 스토리 읽기 고객 사례 섹션으로 돌아가기 파트너 추천 앱 Explore the Microsoft partner ecosystem</h2> "> Microsoft 파트너 에코시스템 살펴보기 Microsoft 파트너의 금융 서비스 소프트웨어로 가치 실현 시간을 단축하고 시장 진입을 가속화하세요. (#=appDisplayName#) (#=appTitle#) (#=appDesc#) (#=averageRating#) ((#=ratingCount#)) (#=ratingCount#)명의 사용자가 별점 5점 만점에 (#=ratingAverage#)점을 매겼습니다. (#=appHelpText#) 콘텐츠 로드 중... 모든 앱 보기 제품 Discover Microsoft products</h2> "> Microsoft 제품 살펴보기 높은 보안과 규정 준수를 갖춘 플랫폼인 Microsoft 클라우드 기반 금융 서비스 소프트웨어와 솔루션을 탐색하세요. 이전 슬라이드 다음 슬라이드 Microsoft Azure Azure로 금융 서비스에 혁신적인 클라우드 솔루션을 만드세요. 자세한 정보 Microsoft Fabric AI 기반의 단일 플랫폼을 사용하여 조직의 모든 사람이 데이터에 액세스하고, 관리하고, 사용합니다. 자세한 정보 Microsoft Power Platform 로우 코드 도구를 사용하여 비용 및 개발 시간을 단축하세요. 자세한 정보 Microsoft 365 Microsoft 365 솔루션을 사용하여 작업 공간 현대화를 촉진하고 위험 노출을 줄입니다. 자세한 정보 Microsoft Teams 최전방 직원을 위한 매우 안전한 도구를 사용하여 커뮤니케이션, 협업, 운영을 향상시킵니다. 자세한 정보 Microsoft 365 Copilot Microsoft 365 Copilot을 사용하여 생산성을 높이고 효율성을 높이고 비즈니스 결과를 개선하세요. 자세한 정보 Microsoft Dynamics 365 팀, 프로세스, 데이터를 연결해 뛰어난 고객 경험을 만들고 운영 민첩성을 높이세요. 자세한 정보 Microsoft Security 플랫폼과 클라우드 환경에서 작동하는 비즈니스 보안 솔루션으로 조직을 보호하세요. 자세한 정보 제품 섹션으로 돌아가기 Meet compliance requirements</h2> "> 규정 준수 요구 사항 충족 DORA(Digital Operational Resilience ACT)를 지원하기 위한 Microsoft의 약속에 대해 알아봅니다. 자세한 정보 Find valuable resources</h2> "> 유용한 리소스 찾기 Navigate security and regulatory concerns in AI adoption</h3> "> 백서 • 2025년 4월 AI 채택에서 보안 및 규제 문제 탐색 금융 서비스 기업이 위험을 관리하고 IT를 현대화하는 방법을 포함하여 AI 채택에 어떻게 접근하고 있는지 살펴보세요. 1 백서 읽기 Efficiency and innovation:&nbsp;The impact of AI on modern banking</h3> "> 비디오 효율성과 혁신: 현대 뱅킹에 미치는 AI의 영향 비디오 보기 Microsoft: The power of partnering with Microsoft</h3> "> 비디오 Microsoft: Microsoft와의 파트너십의 힘 비디오 보기 Improve compliance and security in financial services with AI</h3> "> 비디오 AI로 금융 서비스의 규정 준수와 보안을 향상하세요 비디오 보기 다음 단계 Achieve more in financial services</h2> "> 금융 서비스에서 더 많은 성과 달성 Microsoft AI principles and practices</h3> "> 책임 있는 AI Microsoft AI 원칙 및 관행 Microsoft가 거버넌스, 정책, 연구를 통해 책임 있는 AI 관행을 위해 계속 노력하는 방법을 살펴보세요. 자세한 정보 Microsoft guidance on compliance</h3> "> 규정 준수 마이크로소프트의 규정 준수 가이드 주제 특화 전문가와 소통하여 위험, 감사, 규정 준수 팀을 지원하고 클라우드 채택을 가속화하세요. 자세한 정보 Read Microsoft for Financial Services documentation</h3> "> 설명서 금융 서비스용 Microsoft 설명서 읽기 온라인 교육, 사용법 기사 및 기타 리소스로 마이크로소프트와 파트너 솔루션을 최대한 활용하세요. 지금 살펴보기 규정 준수 문서 를 읽고 보안 센터 를 방문하여 금융 서비스 규정 준수, 데이터 보호 및 개인 정보 보호에 대한 Microsoft의 약속에 대해 자세히 알아보세요. 여기에서 DORA 규정 준수에 대해 여기 에서 자세히 알아보세요. [1] "IDC 백서, 마이크로소프트 후원, 금융 서비스용 GenAI 도입 시 보안 및 규제 문제 탐색, IDC #US53090324, 2025년 4월. 팔로우하기 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 | 2026-01-13T09:29:41 |
https://lever.co/recruiting-resources | Recruiting Resources | Best and Free Recruiting Resources Sales: (888) 885.5299 Sign In Support Solutions AI Companions AI Interview Companion AI Screening Companion Solutions Recruitment Marketing High-Volume Hiring Diversity & Inclusion Hiring Recruitment Automation Recruitment Analytics Recruitment Communication Career Site Builder Solution Add Ons View All Check Out Our Product Guide See Product Guide Resources Learn Blog Hiring & Recruiting Resources Connect Events & Webinars 2025 Benchmarks Report Get the Report Company Company Why Lever What Customers Say Partner Integrations Careers Join our Team Request Demo Pricing eBooks 2025 Job Seeker Nation Report Download Now Recruiting resources to help you take your strategy to the next level. I’d like to The Latest from Lever Case Study How DREAM Charter Schools Build Authentic Teams CASE STUDY Download Now White Paper The Business Value of Employ Download Now Tools ROI Calculator Download Now eBooks 2025 Job Seeker Nation Report Download Now Webinars Crafting a People-First Employee Journey: Balancing Technolo… Download Now eBooks The Hackett Group® Digital World Class® Talent Acquisiti… Download Now Analyst and media inquiries? Please reach out. Contact Us Solutions Applicant Tracking System AI Interview Companion AI Screening Companion Onboarding Recruitment Analytics Recruitment Automation Recruitment Marketing High-Volume Hiring All Solutions Explore Pricing Request a Demo Content Library Events Webinars Blog Partner Integrations Marketplace Compare & Choose Lever vs. Ashby Lever vs. Greenhouse Lever vs. Workable Lever vs. SmartRecruiters iCIMS vs. SmartRecruiters Greenhouse vs Ashby Greenhouse Alternatives Ashby Alternatives Company About Us Customers Careers Contact Us Support Help Center Product Status Support Connect with Us Privacy Policy Terms of Use Security © 2025 Employ Inc. All rights reserved. Employ, JazzHR, Lever, and Jobvite are registered trademarks of Employ, Inc. Terms and conditions, features, support, pricing, and service options subject to change without notice. | 2026-01-13T09:29:41 |
https://peopleofcolorintech.com/articles/the-hidden-biases-behind-chatgpt/ | The Hidden Biases Behind ChatGPT Stories Latest Stories Careers Engineers Designers Data Product Manager Leadership Guides For tech professionals For founders For investors Break into tech Learning To Code Interviews Diversity & Inclusion AI Climate Founders & Startups Venture Capital Africa Crypto More Media & Entertainment Internet Social Media Music Sports Fashion Trends Tech Industry Gaming Security Silicon Valley Regions Latin America Europe Asia Jobs All Jobs Entry Level Jobs Remote Roles $100k+ Roles Only Hire With POCIT Companies Hiring Cummins Inc. Braze Movable Ink Faire Barclays Ziff Davis ezCater Newsletter Sign Up Past Editions Advertise With Us Community Events Work With Us / Partner Stories Latest Stories Careers Engineers Designers Data Product Manager Leadership Guides For tech professionals For founders For investors Break into tech Learning To Code Interviews Diversity & Inclusion AI Climate Founders & Startups Venture Capital Africa Crypto More Media & Entertainment Internet Social Media Music Sports Fashion Trends Tech Industry Gaming Security Silicon Valley Regions Latin America Europe Asia Jobs All Jobs Entry Level Jobs Remote Roles $100k+ Roles Only Hire With POCIT Companies Hiring Cummins Inc. Braze Movable Ink Faire Barclays Ziff Davis ezCater Newsletter Sign Up Past Editions Advertise With Us Community Events Work With Us / Partner December 13, 2022 By Christian Ilube December 13, 2022 in AI , Articles , Diversity & Inclusion , Engineers , Main , Top Stories Comments Off on The Hidden Biases Behind ChatGPT The Hidden Biases Behind ChatGPT This article by Christian Ilube was first published on Medium . What is ChatGPT? Open AI is an artificial intelligence research company that aims to create AI to benefit all of humanity. In 2020, they announced GPT-3 (Generative Pre-trained Transformer 3), an AI capable of any reading/writing task e.g., question answering, summarising text, or continuing a story. It was created as a step on the way to Open AI’s grand mission of solving general intelligence, creating an AI able to learn any intellectual task that a human can do. Despite not being general intelligence, GPT-3 still has many uses. A variety of apps that use it for different tasks have spun out of it as a result. The latest one is called ChatGPT , created by Open AI themselves. It is a chatbot designed for dialogue. Open AI sells some of their products, for instance allowing users to pay to run their programs through APIs . However, their aim is to develop AI in a transparent way, making much of their code and research open source. This means they don’t generate much profit and are heavily reliant on investment , for example, the billion-dollar deal they made with Microsoft shortly after they released GPT-3. The applications they develop are needed to generate hype around their products and attract more investment. Hidden Biases An important consequence of this, is that Open AI do their best to hide any flaws in their systems, that may scare away investors. We saw an example of this recently when they made their DALL.E AI available to the public. DALL.E takes natural language prompts as input and generates pictures of what is written. It was trained on huge datasets of images available on the internet. The pictures in these datasets likely featured a much higher percentage of white males and initially this was reflected in the pictures that DALL.E generated. In order to avoid accusations of bias and maintain hype, Open AI secretly altered the prompts inputted by users by adding extra text such as ‘black female’ at the end of prompts. These were visible to the AI but not the user. Researchers discovered this when they started using prompts such as “a person holding a sign that says” and received images of people holding signs saying, “Black Female”, implying that the words “black female” had secretly been added to the prompt. Image generated by DALL.E https://twitter.com/rzhang88/status/1549472829304741888 This makes the AI appear less biased without actually fixing its inherent problems. Open AI essentially tried to sweep the problem of bias under the rug. This is dangerous because these technologies have the potential to have massive impacts on society, so transparency is needed for us to accurately assess how safe they are to use. GPT-3 suffers from many of the same issues as DALL.E. GPT-3 was trained on a curated version of the common crawl dataset , a dataset made by algorithms that scrape the internet for text data. Experts believe that most of the text on the internet is generated by white males in western countries . It is likely that GPT-3’s training data overrepresents this demographic. Open AI’s own research discovered that the sentiment of the text it generated, varied when talking about different racial groups. GPT-3 Sentiment across racial groups https://arxiv.org/abs/2005.14165 ChatGPT will not engage in any conversations it deems to be inappropriate. This is because Open AI are using their Moderation API , another application made using GPT-3, to block certain types of unsafe content. While this helps to stop mass production of harmful content, it leaves us in the dark about how an unfiltered GPT-3 would respond to certain questions. it is a good thing that Open AI are aware of these limitations and are actively working to fix them , but it may also mean that the public is unaware of the technology’s potential danger to society. Awareness of these dangers will be especially significant when policy makers consider GPT-3 based applications. The moderated responses of ChatGPT, make language AI seem safe to start using today. However, we cannot be so confident in the text generated by Language AI, when they are applied to less structured tasks and given more freedom. There is still work to be done before we start using them everywhere. How many languages can ChatGPT speak? Most of the text data on the internet is in English . Therefore, GPT-3 performs much better in English than any other language. In the brief conversation I had with ChatGPT, I experimented by talking to it in various languages and although it is capable of conversing in an impressive range of languages, it acknowledges that its far more capable in English. ChatGPT’s response to my question White males from western countries have had the largest role in creating this technology. They make up some of the key decision makers behind its creation but more importantly they have contributed the most data to its training set. Similarly, English speaking internet users will benefit the most from this technology. This is a relatively small and affluent section of society so it is fair to say that this technology will widen the inequality gap . Future research Language AI research has made incredibly fast progress in recent years. Applications using GPT-3 have demonstrated impressive capabilities so the hype that surrounds them is not without substance. However, we still have a long way to go before we can be sure that these technologies will benefit all of humanity . It is paramount that the world is aware of the limitations they have, regardless of the effect this may have on investment. This article by Christian Ilube was first published on Medium . Article Tags : AI , AI bias , ChatGPT , OpenAI Share this article Christian Ilube Arts and Sciences undergraduate student at University College London, passionate about tackling algorithmic bias. https://medium.com/@ilubechristian Jobs Companies Hiring POCIT is the world’s leading platform for the underrepresented in tech to share, grow, and get hired. Follow Us Weekly Newsletter Get Hired on POCIT Hire Talent/Recruitment Post A Job Opening Search Talent Get Hired FAQ / Help Contact Us Pricing Other Advertise With Us Techish Podcast Trending Company © POCIT 2021. All rights reserved | 2026-01-13T09:29:41 |
https://support.microsoft.com/es-es/office/-qu%C3%A9-es-turnos-f8efe6e4-ddb3-4d23-b81b-bb812296b821 | ¿Qué es Turnos? - Soporte técnico de Microsoft Temas relacionados × Formación en vídeo de Microsoft Teams Inicio rápido de Microsoft Teams ¿Qué es Microsoft Teams? Iniciar sesión y comenzar a usarlo Chatear y compartir archivos Colaborar Más información Introducción a Microsoft Teams Introducción a Microsoft Teams Introducción al chat Introducción a las reuniones Introducción a las aplicaciones Configurar y personalizar su equipo Crear un equipo con plantillas Trabajar con invitados externos Administrar la configuración del equipo. Colaborar en equipos y canales Consejo: Enviar un correo electrónico a un canal Crear un plan con Planner Trabajar con mensajes y publicaciones Publicar un mensaje en varios canales Buscar y encontrar archivos Cargar y compartir archivos Buscar y filtrar personas y archivos Buscar y filtrar mensajes Recomendaciones para archivos de Teams Comenzar chats y llamadas Información general de las llamadas usando Teams Hacer llamadas Sugerencias para las llamadas de Teams Ocultar chats y eliminar mensajes Configurar un delegado para realizar las llamadas Administrar reuniones Unirse a una reunión de Teams Sugerencias para las reuniones de Teams Reunirse al instante Administrar reuniones Programar un seminario web Mostrar la pantalla durante una reunión Configurar eventos en directo y participar en ellos Planear y programar un evento en directo Producir un evento en directo Asistir a un evento en directo Moderar una sesión de preguntas y respuestas Explorar aplicaciones y herramientas Buscar y usar aplicaciones Administrar programación de equipo con Turnos ¿Qué es Turnos? Crear una programación de turnos Administrar una programación de Turnos Crear aprobaciones ¿Qué es Aprobaciones? Crear una aprobación Crear una aprobación desde un chat Crear una aprobación de firma electrónica Descubrir las plantillas en Aprobaciones Crear aprobaciones con plantillas Crear plantillas para toda la organización Citas virtuales en Microsoft Bookings ¿Qué son las citas virtuales? Enviar notificaciones de texto SMS de invitados externos Realizar una cita Unirse a una cita Administrar su fuente de actividades Administrar la configuración de notificaciones Teams donde quiera que esté Iniciar un chat mientras te desplazas Crea un canal en cualquier lugar Unirse a una reunión donde quiera que esté La fuente de actividades donde quiera que esté Saltar al contenido principal Microsoft Soporte técnico Soporte técnico Soporte técnico Inicio Microsoft 365 Office Soporte técnico de Teams Temas Reuniones Chat Notificaciones y configuración Teams y canales Llamadas & dispositivos Archivos Aplicaciones y servicios Inicio rápido Chat Chat de grupo Notificaciones Teams Canales Llamadas Archivos Aplicaciones Componentes de Loop Novedades Recursos Vídeos de aprendizaje Solucionar problemas Aquí, en Teams Accesibilidad Características de Teams por plataforma Microsoft Teams (gratis) Foros de la comunidad Blog de la comunidad tecnológica Formación dirigida por un instructor Para administradores y profesionales de TI Para la educación Más Comprar Microsoft 365 Todo Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Ofertas Pequeñas empresas Soporte Software Software Aplicaciones Windows IA OneDrive Outlook Paso de Skype a Teams OneNote Microsoft Teams PCs y dispositivos PCs y dispositivos Comprar Xbox Accesorios Entretenimiento Entretenimiento Xbox Game Pass Ultimate Xbox y juegos Juegos para PC Empresas Empresas Seguridad de Microsoft Azure Dynamics 365 Microsoft 365 para empresas Microsoft Industry Microsoft Power Platform Windows 365 Desarrolladores y TI Desarrolladores y TI Desarrollador de Microsoft Microsoft Learn Soporte técnico para aplicaciones del marketplace de IA Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Otro Otro Microsoft Rewards Seguridad y descargas gratuitas Educación Tarjetas regalo Licenciamiento Ver mapa del sitio Buscar Búsqueda de ayuda Sin resultados Cancelar Iniciar sesión Iniciar sesión con Microsoft Iniciar sesión o crear una cuenta Hola: Seleccione una cuenta diferente. Tiene varias cuentas Elija la cuenta con la que desea iniciar sesión. Temas relacionados Formación en vídeo de Microsoft Teams Inicio rápido de Microsoft Teams ¿Qué es Microsoft Teams? Iniciar sesión y comenzar a usarlo Chatear y compartir archivos Colaborar Más información Introducción a Microsoft Teams Introducción a Microsoft Teams Introducción al chat Introducción a las reuniones Introducción a las aplicaciones Configurar y personalizar su equipo Crear un equipo con plantillas Trabajar con invitados externos Administrar la configuración del equipo. Colaborar en equipos y canales Consejo: Enviar un correo electrónico a un canal Crear un plan con Planner Trabajar con mensajes y publicaciones Publicar un mensaje en varios canales Buscar y encontrar archivos Cargar y compartir archivos Buscar y filtrar personas y archivos Buscar y filtrar mensajes Recomendaciones para archivos de Teams Comenzar chats y llamadas Información general de las llamadas usando Teams Hacer llamadas Sugerencias para las llamadas de Teams Ocultar chats y eliminar mensajes Configurar un delegado para realizar las llamadas Administrar reuniones Unirse a una reunión de Teams Sugerencias para las reuniones de Teams Reunirse al instante Administrar reuniones Programar un seminario web Mostrar la pantalla durante una reunión Configurar eventos en directo y participar en ellos Planear y programar un evento en directo Producir un evento en directo Asistir a un evento en directo Moderar una sesión de preguntas y respuestas Explorar aplicaciones y herramientas Buscar y usar aplicaciones Administrar programación de equipo con Turnos ¿Qué es Turnos? Crear una programación de turnos Administrar una programación de Turnos Crear aprobaciones ¿Qué es Aprobaciones? Crear una aprobación Crear una aprobación desde un chat Crear una aprobación de firma electrónica Descubrir las plantillas en Aprobaciones Crear aprobaciones con plantillas Crear plantillas para toda la organización Citas virtuales en Microsoft Bookings ¿Qué son las citas virtuales? Enviar notificaciones de texto SMS de invitados externos Realizar una cita Unirse a una cita Administrar su fuente de actividades Administrar la configuración de notificaciones Teams donde quiera que esté Iniciar un chat mientras te desplazas Crea un canal en cualquier lugar Unirse a una reunión donde quiera que esté La fuente de actividades donde quiera que esté ¿Qué es Turnos? Se aplica a Teams Microsoft Teams ¡Pruébelo! La aplicación Turnos en Microsoft Teams es una herramienta de administración de programación y seguimiento de tiempo que le ayuda a crear, actualizar y administrar programaciones para su equipo. Programaciones : cree, edite y administre una programación para su equipo. Una programación de Turnos muestra los días en la parte superior, los miembros del equipo aparecen a la izquierda y los turnos asignados aparecen en el calendario. Configuración de programación: en la configuración de Turnos, defina las opciones de programación y elija las funcionalidades de Turnos que desea que estén disponibles para su equipo. Grupos : agregue grupos de programación para organizar los miembros del equipo en la programación por tipo de trabajo o ubicación. Turnos : asigne turnos a los miembros del equipo. Cree un turno desde cero o copie uno existente. Turnos abiertos : cada grupo de la programación tiene una fila Turnos abiertos . Agregue turnos abiertos a la programación que cualquiera pueda solicitar. Reloj de hora : active reloj de hora en la configuración de Turnos para permitir que el equipo entre y salga de los turnos. Solicitudes : revise y responda a solicitudes de permisos, turnos abiertos, intercambios de turnos y ofertas. Etiquetas : use etiquetas basadas en turnos para comunicarse rápidamente con cualquier persona que esté actualmente en turnos. Publicar la programación : cuando haya terminado de realizar cambios en la programación, compártalo con su equipo para que todos estén al día. ¿Desea obtener más información? Comenzar a usar Turnos Crear una programación de equipo en Turnos Agregar turnos a la programación en Turnos Publicar una programación en Turnos Administrar solicitudes de turno y permisos en Turnos Activar etiquetas basadas en turnos en Teams SUSCRIBIRSE A FUENTES RSS ¿Necesita más ayuda? ¿Quiere más opciones? Descubrir Comunidad Explore las ventajas de las suscripciones, examine los cursos de aprendizaje, aprenda a proteger su dispositivo y mucho más. Ventajas de la suscripción de Microsoft 365 Aprendizaje de Microsoft 365 <div class="supARG-column-1-4" data-bi-compnm="row-1,col- | 2026-01-13T09:29:41 |
https://fosstodon.org/users/everythingopen | Everything Open Conference (@everythingopen@fosstodon.org) - Fosstodon To use the Mastodon web application, please enable JavaScript. Alternatively, try one of the native apps for Mastodon for your platform. | 2026-01-13T09:29:41 |
https://git-scm.com/book/be/v2/Git-Basics-Working-with-Remotes | Git - Working with Remotes About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Першыя крокі 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Падсумаваньне 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Дадатак A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Дадатак B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Дадатак C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.5 Git Basics - Working with Remotes Working with Remotes To be able to collaborate on any Git project, you need to know how to manage your remote repositories. Remote repositories are versions of your project that are hosted on the Internet or network somewhere. You can have several of them, each of which generally is either read-only or read/write for you. Collaborating with others involves managing these remote repositories and pushing and pulling data to and from them when you need to share work. Managing remote repositories includes knowing how to add remote repositories, remove remotes that are no longer valid, manage various remote branches and define them as being tracked or not, and more. In this section, we’ll cover some of these remote-management skills. Заўвага Remote repositories can be on your local machine. It is entirely possible that you can be working with a “remote” repository that is, in fact, on the same host you are. The word “remote” does not necessarily imply that the repository is somewhere else on the network or Internet, only that it is elsewhere. Working with such a remote repository would still involve all the standard pushing, pulling and fetching operations as with any other remote. Showing Your Remotes To see which remote servers you have configured, you can run the git remote command. It lists the shortnames of each remote handle you’ve specified. If you’ve cloned your repository, you should at least see origin — that is the default name Git gives to the server you cloned from: $ git clone https://github.com/schacon/ticgit Cloning into 'ticgit'... remote: Reusing existing pack: 1857, done. remote: Total 1857 (delta 0), reused 0 (delta 0) Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done. Resolving deltas: 100% (772/772), done. Checking connectivity... done. $ cd ticgit $ git remote origin You can also specify -v , which shows you the URLs that Git has stored for the shortname to be used when reading and writing to that remote: $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) If you have more than one remote, the command lists them all. For example, a repository with multiple remotes for working with several collaborators might look something like this. $ cd grit $ git remote -v bakkdoor https://github.com/bakkdoor/grit (fetch) bakkdoor https://github.com/bakkdoor/grit (push) cho45 https://github.com/cho45/grit (fetch) cho45 https://github.com/cho45/grit (push) defunkt https://github.com/defunkt/grit (fetch) defunkt https://github.com/defunkt/grit (push) koke git://github.com/koke/grit.git (fetch) koke git://github.com/koke/grit.git (push) origin git@github.com:mojombo/grit.git (fetch) origin git@github.com:mojombo/grit.git (push) This means we can pull contributions from any of these users pretty easily. We may additionally have permission to push to one or more of these, though we can’t tell that here. Notice that these remotes use a variety of protocols; we’ll cover more about this in Getting Git on a Server . Adding Remote Repositories We’ve mentioned and given some demonstrations of how the git clone command implicitly adds the origin remote for you. Here’s how to add a new remote explicitly. To add a new remote Git repository as a shortname you can reference easily, run git remote add <shortname> <url> : $ git remote origin $ git remote add pb https://github.com/paulboone/ticgit $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) pb https://github.com/paulboone/ticgit (fetch) pb https://github.com/paulboone/ticgit (push) Now you can use the string pb on the command line in lieu of the whole URL. For example, if you want to fetch all the information that Paul has but that you don’t yet have in your repository, you can run git fetch pb : $ git fetch pb remote: Counting objects: 43, done. remote: Compressing objects: 100% (36/36), done. remote: Total 43 (delta 10), reused 31 (delta 5) Unpacking objects: 100% (43/43), done. From https://github.com/paulboone/ticgit * [new branch] master -> pb/master * [new branch] ticgit -> pb/ticgit Paul’s master branch is now accessible locally as pb/master — you can merge it into one of your branches, or you can check out a local branch at that point if you want to inspect it. We’ll go over what branches are and how to use them in much more detail in Git Branching . Fetching and Pulling from Your Remotes As you just saw, to get data from your remote projects, you can run: $ git fetch <remote> The command goes out to that remote project and pulls down all the data from that remote project that you don’t have yet. After you do this, you should have references to all the branches from that remote, which you can merge in or inspect at any time. If you clone a repository, the command automatically adds that remote repository under the name “origin”. So, git fetch origin fetches any new work that has been pushed to that server since you cloned (or last fetched from) it. It’s important to note that the git fetch command only downloads the data to your local repository — it doesn’t automatically merge it with any of your work or modify what you’re currently working on. You have to merge it manually into your work when you’re ready. If your current branch is set up to track a remote branch (see the next section and Git Branching for more information), you can use the git pull command to automatically fetch and then merge that remote branch into your current branch. This may be an easier or more comfortable workflow for you; and by default, the git clone command automatically sets up your local master branch to track the remote master branch (or whatever the default branch is called) on the server you cloned from. Running git pull generally fetches data from the server you originally cloned from and automatically tries to merge it into the code you’re currently working on. Заўвага From git version 2.27 onward, git pull will give a warning if the pull.rebase variable is not set. Git will keep warning you until you set the variable. If you want the default behavior of git (fast-forward if possible, else create a merge commit): git config --global pull.rebase "false" If you want to rebase when pulling: git config --global pull.rebase "true" Pushing to Your Remotes When you have your project at a point that you want to share, you have to push it upstream. The command for this is simple: git push <remote> <branch> . If you want to push your master branch to your origin server (again, cloning generally sets up both of those names for you automatically), then you can run this to push any commits you’ve done back up to the server: $ git push origin master This command works only if you cloned from a server to which you have write access and if nobody has pushed in the meantime. If you and someone else clone at the same time and they push upstream and then you push upstream, your push will rightly be rejected. You’ll have to fetch their work first and incorporate it into yours before you’ll be allowed to push. See Git Branching for more detailed information on how to push to remote servers. Inspecting a Remote If you want to see more information about a particular remote, you can use the git remote show <remote> command. If you run this command with a particular shortname, such as origin , you get something like this: $ git remote show origin * remote origin Fetch URL: https://github.com/schacon/ticgit Push URL: https://github.com/schacon/ticgit HEAD branch: master Remote branches: master tracked dev-branch tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) It lists the URL for the remote repository as well as the tracking branch information. The command helpfully tells you that if you’re on the master branch and you run git pull , it will automatically merge the remote’s master branch into the local one after it has been fetched. It also lists all the remote references it has pulled down. That is a simple example you’re likely to encounter. When you’re using Git more heavily, however, you may see much more information from git remote show : $ git remote show origin * remote origin URL: https://github.com/my-org/complex-project Fetch URL: https://github.com/my-org/complex-project Push URL: https://github.com/my-org/complex-project HEAD branch: master Remote branches: master tracked dev-branch tracked markdown-strip tracked issue-43 new (next fetch will store in remotes/origin) issue-45 new (next fetch will store in remotes/origin) refs/remotes/origin/issue-11 stale (use 'git remote prune' to remove) Local branches configured for 'git pull': dev-branch merges with remote dev-branch master merges with remote master Local refs configured for 'git push': dev-branch pushes to dev-branch (up to date) markdown-strip pushes to markdown-strip (up to date) master pushes to master (up to date) This command shows which branch is automatically pushed to when you run git push while on certain branches. It also shows you which remote branches on the server you don’t yet have, which remote branches you have that have been removed from the server, and multiple local branches that are able to merge automatically with their remote-tracking branch when you run git pull . Renaming and Removing Remotes You can run git remote rename to change a remote’s shortname. For instance, if you want to rename pb to paul , you can do so with git remote rename : $ git remote rename pb paul $ git remote origin paul It’s worth mentioning that this changes all your remote-tracking branch names, too. What used to be referenced at pb/master is now at paul/master . If you want to remove a remote for some reason — you’ve moved the server or are no longer using a particular mirror, or perhaps a contributor isn’t contributing anymore — you can either use git remote remove or git remote rm : $ git remote remove paul $ git remote origin Once you delete the reference to a remote this way, all remote-tracking branches and configuration settings associated with that remote are also deleted. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://git-scm.com/book/sv/v2/Grunder-i-Git-Jobba-med-fj%c3%a4rrf%c3%b6rvar | Git - Jobba med fjärrförvar About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Bilaga A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in PowerShell A1.7 Summary A2. Bilaga B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Bilaga C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.5 Grunder i Git - Jobba med fjärrförvar Jobba med fjärrförvar För att kunna samarbeta i ett Gitprojekt, behöver du veta hur du hanterar dina fjärrförvar. Fjärrförvar är versioner av ditt projekt som finns på Internet eller ett nätverk någonstans. Du kan ha flera, en som normalt är skrivskyddat eller skrivbart endast för dig. Att jobba med andra innebär att hantera dessa fjärrförvar och skicka och hämta data till och från dem när du behöver delge det du producerat. Att hanterara fjärrförvar inbegriper att veta hur du lägger till dem, tar bort sådana som inte längre är giltiga, hantera grenar på fjärrförvaren och definera dem som spårade eller inte, och mycket annat. I detta avsnitt kommer vi att täcka en del av dessa koncepten. Notera Fjärrförvar kan även vara på din lokala maskin. Det är fullt möjligt att du kan jobba mot ett “fjärr''förvar som är på samma värdmaskin som du jobbar på. Ordet ``fjärr” betyder nödvändigtvis inte att förvaret finns på nätverket eller Internet, bara att det finns någon annanstans. Att jobba med ett sådant fjärrförvar inbegriper fortfarande samma sätt att skicka, hämta och applicara ändringar. Visa dina fjärrförvar För att se vilka fjärrförvar du har konfigurerade kan du köra kommandot git remote . Det listar namnen på varje fjärrförvar du har specificerat. Om du har klonat ditt förvar, borde du åtminstone se origin — det är standardnamnet som Git ger den server du klonat ditt förvar ifrån: $ git clone https://github.com/schacon/ticgit Cloning into 'ticgit'... remote: Reusing existing pack: 1857, done. remote: Total 1857 (delta 0), reused 0 (delta 0) Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done. Resolving deltas: 100% (772/772), done. Checking connectivity... done. $ cd ticgit $ git remote origin Du kan också specificera -v som även visar dig sökvägen som Git har sparat för varje namn som används när du hämtar eller skickar data till eller från fjärrförvaret: $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) Om du har mer än ett fjärrförvar listar kommandot alla. Som exempel kan ett förvar med flera fjärrförvar för att arbeta med flera olika kollaboratörer se ut något i stil med detta. $ cd grit $ git remote -v bakkdoor https://github.com/bakkdoor/grit (fetch) bakkdoor https://github.com/bakkdoor/grit (push) cho45 https://github.com/cho45/grit (fetch) cho45 https://github.com/cho45/grit (push) defunkt https://github.com/defunkt/grit (fetch) defunkt https://github.com/defunkt/grit (push) koke git://github.com/koke/grit.git (fetch) koke git://github.com/koke/grit.git (push) origin git@github.com:mojombo/grit.git (fetch) origin git@github.com:mojombo/grit.git (push) Detta betyder att vi kan hämta bidrag från vilken som helst av dessa ganska enkelt. Utöver det kanske vi har rättigheter att skicka ändringar till en eller flera av dessa, men det kan vi inte avgöra här. Notera att dessa fjärrförvar använder varierande protokoll; vi kommer behandla detta mer i Skaffa Git på en server . Lägga till fjärrförvar Vi har nämnt och givit lite demonstrationer av hur kommandot git clone implicit lägger till origin som fjärrförvar för dig. Såhär gör du för att manuellt lägga till ett nytt fjärrförvar. För att lägga till ett nytt fjärrförvar i Git som ett namn som du lätt kan referera till, kör git remote add <namn> <url> : $ git remote origin $ git remote add pb https://github.com/paulboone/ticgit $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) pb https://github.com/paulboone/ticgit (fetch) pb https://github.com/paulboone/ticgit (push) Nu kan du använda namnet pb på kommandoraden istället för hela sökvägen. Om du till exempel vill hämta all information som Paul har men som du inte har i ditt lokala förvar, kan du köra git fetch pb : $ git fetch pb remote: Counting objects: 43, done. remote: Compressing objects: 100% (36/36), done. remote: Total 43 (delta 10), reused 31 (delta 5) Unpacking objects: 100% (43/43), done. From https://github.com/paulboone/ticgit * [new branch] master -> pb/master * [new branch] ticgit -> pb/ticgit Pauls master-gren är nu tillgänglig lokalt som pb/master — du kan slå samman dessa ändringar in i någon av dina grenar eller du kan checka ut en lokal gren av samma version om du vill inspektera den. (Vi kommer gå igenom vad grenar är och hur du använder dem i mer detalj i Git förgreningar .) Hämta och uppdatera från dina fjärrförvar Som du just såg kan du hämta data från dina fjärrprojekt genom: $ git fetch <fjärrnamn> Kommandot går ut till fjärrprojektet och hämtar hem all data från projektet som du ännu inte har. Efter att du gjort detta har du referenser till alla grenar på fjärrförvaret som du kan slå samman med dina ändringar eller inspektera när du helst vill. Om du klonar ett förvar lägger kommandot automatiskt till det fjärrförvaret under namnet “origin”. Så git fetch origin hämtar allt nytt arbete som har blivit skickat till fjärrförvaret sedan du klonade (eller senast hämtade data) från det. Det är viktigt att att kommandot git fetch bara laddar ner data till ditt lokala förvar — det slår inte automatiskt ihop det med något av ditt arbete eller ändrar det du just nu jobbar med. Du måste manuellt införliva ändringarna i ditt arbete när du är redo. Om du nuvarande gren är inställd på att spåra en fjärrgren (se nästa avsnitt och Git förgreningar för mer information), kan du använda kommandot git pull för att hämta och därefter slå ihop ändringarna i din aktuella gren. Detta kan vara enklare eller mer bekvämt arbetssätt för dig; och normalt gör kommandot git clone att din lokala master-gren spårar motsvarande gren i fjärrförvaret (standardnamnet i fjärrförvaret behöver inte vara master) som du klonade från. Kommandot git pull hämtar generellt data från servern du ursprungligen klonade ifrån och försöker automatiskt att slå ihop ändringarna i den du just nu jobbar med. Skicka till dina fjärrförvar Näär du har ett projekt som du någon gång vill dela med dig av måste du skicka det uppströms. Kommandot för detta är simpelt: git push <fjärrnamn> <gren> . Om du vill skicka upp din master-gren till din origin server (igen, kloning ställer normalt in båda dessa namn för dig automatiskt), då kan du köra detta för att skicka dina versioner upp till servern: $ git push origin master Kommandot fungerar bara om du klonat från en server dit du har skrivrättigheter och om ingen har skickat ändringar under tiden. Om du och någon annan klonar samtidigt och de skickar upp ändringar före dig kommer din sändning självklart att avvisas. Du måste då hämta deras arbete färst och inkorporera i dina innan du tillåts skicka upp din version. Se Git förgreningar för mer detaljerad information om hur du skickar till fjärrservrar. Inspektera ett fjärrförvar Om du vill se mer information om en specifikt fjärrförvar, kan du använda kommandot git remote show <remote> . Om du kör detta kommando med ett specifikt namn, som till exempel origin får du något i stil med: $ git remote show origin * remote origin Fetch URL: https://github.com/schacon/ticgit Push URL: https://github.com/schacon/ticgit HEAD branch: master Remote branches: master tracked dev-branch tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) Det listar sökväg för fjärrförvaret samt information om spårade grenar. Kommandot säger även till dig att om du är på master-grenen och kör git pull , kommer den automatiskt slå samman ändringar med master-grenen på ditt fjärrförvar efter att den hämtat alla fjärreferenser. Den listar också alla fjärreferenser som den har hämtat. Detta är ett simpelt exempel som du sannerligen kommer att stöta på. När du använder Git lite mer kommer du att få mer information från git remote show : $ git remote show origin * remote origin URL: https://github.com/my-org/complex-project Fetch URL: https://github.com/my-org/complex-project Push URL: https://github.com/my-org/complex-project HEAD branch: master Remote branches: master tracked dev-branch tracked markdown-strip tracked issue-43 new (next fetch will store in remotes/origin) issue-45 new (next fetch will store in remotes/origin) refs/remotes/origin/issue-11 stale (use 'git remote prune' to remove) Local branches configured for 'git pull': dev-branch merges with remote dev-branch master merges with remote master Local refs configured for 'git push': dev-branch pushes to dev-branch (up to date) markdown-strip pushes to markdown-strip (up to date) master pushes to master (up to date) Kommadot visar också viklen gren som automatiskt skickas om du gör git push och står i en specifik gren. Den visar också vilka fjärrgrenar på servern som du inte har, och sådana du har men som blivit borttagna från servern, och flera lokala grenar som du automatiskt kan slå ihop ändringar med sin spårade gren då du kör git pull . Byta namn på och ta bort fjärrförvar Du kan köra git remote rename för att änbdra ett fjärförvars namn. Om du till exempel vill byta namn på pb till paul kan du göra det med git remote rename : $ git remote rename pb paul $ git remote origin paul Det skall tilläggas att detta ändrar alla dina spårade grennamn också. Det du tidigare refererade till pb/master är nu paul/master . Om du vill ta bort ett fjärrförvar av någon anledning — du har flyttat servern eller använder inte längre en specifik server, eller så kanske en tidigare medarbetare slutat — så kan du antingen använda git remote remove eller git remote rm : $ git remote remove paul $ git remote origin När du väl tagit bort en referens på detta sättet kommer alla spårade grenar och konfigurationsinställningar som associerades med det fjärrförvaret också att tas bort. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://huggingface.co/yjernite | yjernite (Yacine Jernite) Hugging Face Models Datasets Spaces Community Docs Enterprise Pricing Log In Sign Up 15.1 TFLOPS 77 360 622 Yacine Jernite PRO yjernite Follow Pclanglais's profile picture Wene1's profile picture leeiris's profile picture 385 followers · 575 following https://yjernite.github.io/ YJernite yjernite yacine-jernite-997ba81b6 yjernite.bsky.social AI & ML interests Technical, community, and regulatory tools of AI governance @HuggingFace Recent Activity updated a dataset about 8 hours ago hfmlsoc/sp500_dataset_sec_10q_annotations upvoted a paper about 13 hours ago A Field Guide to Deploying AI Agents in Clinical Practice updated a dataset about 18 hours ago hfmlsoc/sp500_dataset_sec_10k_earnings View all activity Organizations Posts 7 view post Post div]:flex [&>div]:items-center"> 2645 Tremendous quality of life upgrade on the Hugging Face Hub - we now have auto-complete emojis 🤗 🥳 👏 🙌 🎉 Get ready for lots more very serious analysis on a whole range of topics from yours truly now that we have unlocked this full range of expression 😄 🤔 🗣 🙊 See translation View all Posts Articles 33 Article 8 Open Collaboration in Action: Inside the Open Safeguard Hackathon View all Articles Collections 6 Text embedding models I use google/embeddinggemma-300m Sentence Similarity • 0.3B • Updated Sep 25, 2025 • 587k • • 1.41k Qwen/Qwen3-Embedding-0.6B Feature Extraction • 0.6B • Updated Jun 20, 2025 • 2.76M • • 821 Qwen/Qwen3-Embedding-4B-GGUF 4B • Updated Aug 3, 2025 • 9.27k • 81 ibm-granite/granite-embedding-english-r2 Feature Extraction • 0.1B • Updated 7 days ago • 54.8k • 76 super-smol to fine-tune HuggingFaceTB/SmolLM2-135M Text Generation • 0.1B • Updated Feb 6, 2025 • 406k • 152 HuggingFaceTB/SmolLM2-135M-Instruct Text Generation • 0.1B • Updated Sep 22, 2025 • 282k • 278 google/gemma-3-270m Text Generation • 0.3B • Updated Aug 14, 2025 • 46k • 954 google/gemma-3-270m-it Text Generation • 0.3B • Updated Aug 14, 2025 • 99k • 521 Text embedding models I use google/embeddinggemma-300m Sentence Similarity • 0.3B • Updated Sep 25, 2025 • 587k • • 1.41k Qwen/Qwen3-Embedding-0.6B Feature Extraction • 0.6B • Updated Jun 20, 2025 • 2.76M • • 821 Qwen/Qwen3-Embedding-4B-GGUF 4B • Updated Aug 3, 2025 • 9.27k • 81 ibm-granite/granite-embedding-english-r2 Feature Extraction • 0.1B • Updated 7 days ago • 54.8k • 76 super-smol to fine-tune HuggingFaceTB/SmolLM2-135M Text Generation • 0.1B • Updated Feb 6, 2025 • 406k • 152 HuggingFaceTB/SmolLM2-135M-Instruct Text Generation • 0.1B • Updated Sep 22, 2025 • 282k • 278 google/gemma-3-270m Text Generation • 0.3B • Updated Aug 14, 2025 • 46k • 954 google/gemma-3-270m-it Text Generation • 0.3B • Updated Aug 14, 2025 • 99k • 521 View 6 collections Papers 34 arxiv: 2506.22183 arxiv: 2503.16861 arxiv: 2502.16701 arxiv: 2408.16961 Expand 34 papers spaces 7 Sort: Recently updated Sleeping Labor Archive Backend 📚 A backend Space for the labor news archive yjernite 25 days ago Sleeping 3 Llm Moderation Testing 🦀 A model to test different models assessing content policies yjernite Dec 4, 2025 Sleeping News coverage of AI & Labor 🗺 Visualizing articles on the ropic of AI x Labor yjernite Jul 22, 2025 Running Ai Flaw Report Form 🐠 AI Flaw & Incident Report Form yjernite Jun 27, 2025 Sleeping Leaderboard Yourbench Yjernite Yourbench-ipcc-QA 🌍 Display and analyze model leaderboard results yjernite May 14, 2025 Running 8 Space Privacy 📚 Analysing privacy concerns in deployed Spaces yjernite Apr 16, 2025 View 7 Spaces models 2 Sort: Recently updated yjernite/retribert-base-uncased Feature Extraction • Updated Mar 10, 2021 • 883 • 1 yjernite/bart_eli5 Updated Mar 9, 2021 • 255 • 11 datasets 60 Sort: Recently updated yjernite/moderation-test-results Viewer • Updated Dec 2, 2025 • 18 • 24 yjernite/lm_lit_review_corpus-ai_labor_impact Viewer • Updated Nov 19, 2025 • 1.58k • 3 yjernite/lm_lit_review_corpus-ai_monopoly_dynamics Viewer • Updated Nov 19, 2025 • 1.18k • 7 yjernite/lm_lit_review_corpus-ai_efficiency_selection Viewer • Updated Nov 18, 2025 • 597 • 9 yjernite/spaces-privacy-reports Updated Oct 29, 2025 • 197 yjernite/ai-economy-labor-articles-annotated-embed Viewer • Updated Sep 5, 2025 • 25.1k • 69 • 2 yjernite/ai-economy-labor-articles-annotated Viewer • Updated Aug 13, 2025 • 28.3k • 114 yjernite/ai-economy-labor-articles-annotated-processed Viewer • Updated Aug 13, 2025 • 33.3k • 71 • 1 yjernite/ai-economy-labor-articles-annotated-with-embeddings Viewer • Updated Aug 12, 2025 • 33.3k • 121 • 1 yjernite/news-economy-coverage-annotations Viewer • Updated Aug 11, 2025 • 38k • 385 View 60 datasets System theme Company TOS Privacy About Careers Website Models Datasets Spaces Pricing Docs | 2026-01-13T09:29:41 |
https://git-scm.com/book/ru/v2/%d0%92%d0%b5%d1%82%d0%b2%d0%bb%d0%b5%d0%bd%d0%b8%d0%b5-%d0%b2-Git-%d0%a0%d0%b0%d0%b1%d0%be%d1%82%d0%b0-%d1%81-%d0%b2%d0%b5%d1%82%d0%ba%d0%b0%d0%bc%d0%b8 | Git - Работа с ветками About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 3.4 Ветвление в Git - Работа с ветками Работа с ветками Теперь, когда вы познакомились с основами ветвления и слияния, возникает вопрос: что можно или нужно делать с этим? В этом разделе мы разберём некоторые основные рабочие процессы, ставшие возможными благодаря облегчённой процедуре ветвления, которые вы возможно захотите применить в собственном цикле разработки. Долгоживущие ветки Так как в Git применяется простое трёхстороннее слияние, ничто не мешает многократно объединять ветки в течение длительного времени. Это значит, что у вас может быть несколько постоянно открытых веток, которые вы используете для разных этапов вашего цикла разработки; вы можете регулярно сливать изменения из одной ветки в другую. Многие разработчики, использующие Git, придерживаются именно такого подхода, оставляя полностью стабильный код только в ветке master — возможно, только тот код, который был или будет выпущен. При этом существует и параллельная ветка с именем develop или next , предназначенная для работы и тестирования стабильности; она не обязательно должна быть всегда стабильной, но при достижении стабильного состояния её содержимое можно слить в ветку master . Она используется для слияния завершённых задач из тематических веток (временных веток наподобие iss53 ), чтобы гарантировать, что эти задачи проходят тестирование и не вносят ошибок. По сути, мы говорим про указатели, перемещающиеся по линии создаваемых вами коммитов. Стабильные ветки находятся в нижнем конце истории коммитов, а самые свежие наработки — ближе к её верхней части Рисунок 26. Линейное представление повышения стабильности веток В общем случае это можно представить в виде накопителей, в которых наборы коммитов перемещаются на более стабильный уровень только после полного тестирования. Рисунок 27. Представление диаграммы стабильности веток в виде многоуровневого накопителя Число уровней стабильности можно увеличить. В крупных проектах зачастую появляется ветка proposed или pu (предлагаемые обновления), объединяющая ветки с содержимым, которое ещё не готово к включению в ветки next или master . Идея состоит в том, что каждая ветка представляет собой определённый уровень стабильности; как только он повышается, содержимое сливается в ветку уровнем выше. Разумеется, можно вообще обойтись без долгоживущих веток, но зачастую они имеют смысл, особенно при работе над большими и сложными проектами. Тематические ветки А вот такая вещь, как тематические ветки, полезна вне зависимости от величины проекта. Тематической веткой называется временная ветка, создаваемая и используемая для работы над конкретной функциональной возможностью или решения сопутствующих задач. Скорее всего, при работе с другими системами контроля версий вы никогда ничего подобного не делали, так как там создание и слияние веток — затратные операции. Но в Git это обычное дело — много раз в день создавать ветки, работать с ними, сливать их и удалять. Пример тематических веток вы видели в предыдущем разделе, когда мы создавали ветки iss53 и hotfix . В каждой из них было создано несколько коммитов, после чего, сразу же после слияния с основной веткой, они были удалены. Такая техника позволяет быстро и полностью осуществлять переключения контекста — так как работа разделена по уровням и все изменения в конкретной ветке относятся к определённой теме, что позволяет легко увидеть что именно было сделано во время процедуры просмотра кода или аналогичной. Ветки с внесёнными в них изменениями можно хранить минуты, дни или даже месяцы, а слияние выполнить только когда это действительно потребуется, вне зависимости от порядка их создания. Предположим, мы работаем в ветке master , ответвляемся для решения попутной проблемы ( iss91 ), некоторое время занимаемся ею, затем создаём ветку, чтобы попробовать решить эту задачу другим способом ( iss91v2 ), возвращаемся в ветку master и выполняем там некие действия, затем создаём новую ветку для изменений, в результате которых не уверены (ветка dumbidea ). Результирующая история коммитов будет выглядеть примерно так: Рисунок 28. Набор тематических веток Предположим, вам больше нравится второй вариант решения задачи ( iss91v2 ), а ветку dumbidea вы показали коллегам, и оказалось, что там содержится гениальная идея. Фактически вы можете удалить ветку iss91 (потеряв коммиты C5 и C6 ) и слить две другие ветки. После этого история будет выглядеть так: Рисунок 29. История после слияния веток dumbidea и iss91v2 Более подробно возможные варианты рабочих схем для проектов рассматриваются в главе Распределённый Git , поэтому перед выбором схемы обязательно прочитайте эту главу. Важно помнить, что во время всех этих манипуляций ветки полностью локальны. Ветвления и слияния выполняются только в вашем Git репозитории — связь с сервером не требуется. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.digitalcameraworld.com%2Fcameras%2Flenses%2F12-lenses-of-christmas-laowa-and-viltrox-try-to-outdo-each-other-for-most-new-lenses-in-the-same-month&media=https%3A%2F%2Fcdn.mos.cms.futurecdn.net%2FB7uLrQzjBqxjbATn5yZFSK.jpg | Pinterest :root{--sema-space-negative-1600:-64px;--sema-space-negative-1500:-60px;--sema-space-negative-1400:-56px;--sema-space-negative-1300:-52px;--sema-space-negative-1200:-48px;--sema-space-negative-1100:-44px;--sema-space-negative-1000:-40px;--sema-space-negative-900:-36px;--sema-space-negative-800:-32px;--sema-space-negative-700:-28px;--sema-space-negative-600:-24px;--sema-space-negative-500:-20px;--sema-space-negative-400:-16px;--sema-space-negative-350:-14px;--sema-space-negative-300:-12px;--sema-space-negative-250:-10px;--sema-space-negative-200:-8px;--sema-space-negative-150:-6px;--sema-space-negative-100:-4px;--sema-space-negative-50:-2px;--sema-space-negative-25:-1px;--sema-space-1600:64px;--sema-space-1500:60px;--sema-space-1400:56px;--sema-space-1300:52px;--sema-space-1200:48px;--sema-space-1100:44px;--sema-space-1000:40px;--sema-space-900:36px;--sema-space-800:32px;--sema-space-700:28px;--sema-space-600:24px;--sema-space-500:20px;--sema-space-400:16px;--sema-space-350:14px;--sema-space-300:12px;--sema-space-250:10px;--sema-space-200:8px;--sema-space-150:6px;--sema-space-100:4px;--sema-space-50:2px;--sema-space-25:1px;--sema-space-0:0px;--sema-rounding-circle:50%;--sema-rounding-pill:999px;--sema-rounding-800:32px;--sema-rounding-700:28px;--sema-rounding-600:24px;--sema-rounding-500:20px;--sema-rounding-400:16px;--sema-rounding-300:12px;--sema-rounding-200:8px;--sema-rounding-150:6px;--sema-rounding-100:4px;--sema-rounding-0:0px;--sema-opacity-100:1;--sema-opacity-90:0.9;--sema-opacity-80:0.8;--sema-opacity-60:0.6;--sema-opacity-40:0.4;--sema-opacity-20:0.2;--sema-opacity-4:0.04;--sema-opacity-0:0;--sema-elevation-background-blur-strong:64px;--sema-elevation-background-blur-default:24px;--sema-elevation-background-blur-weak:8px;--sema-elevation-shadow-floating:0px 3px 12px 0px rgba(0,0,0,.2);--sema-elevation-shadow-raised:0px 1.5px 6px 0px rgba(0,0,0,.2);--sema-elevation-shadow-surface:0px 0.5px 3px 0px rgba(0,0,0,.2);--sema-color-pressed-icon-performance-plus:#583b91;--sema-color-pressed-background-wash-scrims-opaque:hsla(60,3%,74%,.8);--sema-color-pressed-background-wash-scrims-default:rgba(29,29,27,.4);--sema-color-pressed-background-wash-image-tint:rgba(57,57,55,.14);--sema-color-pressed-background-wash-light:hsla(60,30%,91%,.5);--sema-color-pressed-background-wash-dark:rgba(11,11,10,.5);--sema-color-pressed-background-wash-inverse:rgba(11,11,10,.5);--sema-color-pressed-background-wash-default:hsla(60,30%,91%,.5);--sema-color-pressed-background-performance-plus-weak:#cbb5f5;--sema-color-pressed-background-performance-plus-default:#583b91;--sema-color-hover-icon-performance-plus:#6845ab;--sema-color-hover-background-wash-scrims-opaque:hsla(60,6%,83%,.8);--sema-color-hover-background-wash-scrims-default:rgba(51,51,46,.4);--sema-color-hover-background-wash-image-tint:rgba(36,36,35,.09);--sema-color-hover-background-wash-light:hsla(60,14%,96%,.5);--sema-color-hover-background-wash-dark:rgba(24,24,22,.5);--sema-color-hover-background-wash-inverse:rgba(24,24,22,.5);--sema-color-hover-background-wash-default:hsla(60,14%,96%,.5);--sema-color-hover-background-performance-plus-weak:#dccdfa;--sema-color-hover-background-performance-plus-default:#6845ab;--sema-color-dataviz-neutral:#767676;--sema-color-dataviz-09:#f2681f;--sema-color-dataviz-08:#400387;--sema-color-dataviz-07:#00ab55;--sema-color-dataviz-06:#ff5383;--sema-color-dataviz-05:#0081fe;--sema-color-dataviz-04:#d17711;--sema-color-dataviz-03:#924af7;--sema-color-dataviz-02:#11a69c;--sema-color-dataviz-01:#003c96;--sema-color-dataviz-12:#660e00;--sema-color-dataviz-11:#de2c62;--sema-color-dataviz-10:#005062;--sema-color-icon-performance-plus:#774fc4;--sema-color-background-gradient-darken-top-strong:linear-gradient(0deg,transparent,rgba(0,0,0,.8));--sema-color-background-gradient-darken-top-weak:linear-gradient(0deg,transparent,rgba(0,0,0,.4));--sema-color-background-gradient-darken-bottom-strong:linear-gradient(180deg,transparent,rgba(0,0,0,.8));--sema-color-background-gradient-darken-bottom-weak:linear-gradient(180deg,transparent,rgba(0,0,0,.4));--sema-color-background-wash-scrims-opaque:hsla(60,9%,89%,.8);--sema-color-background-wash-scrims-default:rgba(73,73,67,.4);--sema-color-background-wash-image-tint:rgba(0,0,0,.04);--sema-color-background-wash-light:hsla(60,20%,98%,.5);--sema-color-background-wash-dark:rgba(36,36,33,.5);--sema-color-background-wash-inverse:rgba(36,36,33,.5);--sema-color-background-wash-default:hsla(60,20%,98%,.5);--sema-color-background-performance-plus-weak:#ebe2fd;--sema-color-background-performance-plus-default:#774fc4;--sema-color-background-transparent:hsla(0,0%,100%,0);--comp-switch-size-width-handle-disabled-on:20px;--comp-switch-size-width-handle-disabled-off:22px;--comp-switch-size-width-handle-enabled-on:20px;--comp-switch-size-width-handle-enabled-off:22px;--comp-switch-size-height-handle-disabled-on:20px;--comp-switch-size-height-handle-disabled-off:22px;--comp-switch-size-height-handle-enabled-on:20px;--comp-switch-size-height-handle-enabled-off:22px;--comp-switch-border-width-container-off:0px;--comp-switch-border-width-container-on:0px;--comp-spinner-color-background-3:#22a596;--comp-spinner-color-background-2:#e57534;--comp-spinner-color-background-1:#c85bd2;--comp-searchguide-border-width-focus-outer:2;--comp-searchguide-border-width-focus-inner:2;--comp-searchguide-color-background-rainbow-default:linear-gradient(-60deg,#d4b0ff,#90f0e1 37%,#c7f783 66%,#ffa570);--comp-radiobutton-border-width-focus-outer:2px;--comp-radiobutton-border-width-focus-inner:2px;--comp-radiobutton-border-width-pressed-container-disabled-selected:0px;--comp-radiobutton-border-width-pressed-container-disabled-deselected:0px;--comp-radiobutton-border-width-pressed-container-default-selected:0px;--comp-radiobutton-border-width-pressed-container-default-deselected:2px;--comp-radiobutton-border-width-hover-container-disabled-selected:0px;--comp-radiobutton-border-width-hover-container-disabled-deselected:0px;--comp-radiobutton-border-width-hover-container-default-selected:0px;--comp-radiobutton-border-width-hover-container-default-deselected:2px;--comp-radiobutton-border-width-container-disabled-selected:0px;--comp-radiobutton-border-width-container-disabled-deselected:0px;--comp-radiobutton-border-width-container-default-selected:0px;--comp-radiobutton-border-width-container-default-deselected:1px;--comp-indicator-border-width-numeric:1px;--comp-indicator-border-width-default:0px;--comp-iconbuttonsocial-color-pressed-background-wash-container:rgba(57,57,55,.14);--comp-iconbuttonsocial-color-hover-background-wash-container:rgba(36,36,35,.09);--comp-iconbuttonsocial-color-background-wash-container:transparent;--comp-iconbuttonsocial-color-background-container-samsung-messages:linear-gradient(180deg,#4189ed,#376df6);--comp-iconbuttonsocial-color-background-container-discord:#5865f2;--comp-iconbuttonsocial-color-background-container-instagram-stories:#ff0076;--comp-iconbuttonsocial-color-background-container-instagram:#ff0076;--comp-iconbuttonsocial-color-background-container-facebook-stories:#0866ff;--comp-iconbuttonsocial-color-background-container-viber:#7360f2;--comp-iconbuttonsocial-color-background-container-threads:#000;--comp-iconbuttonsocial-color-background-container-wechat:linear-gradient(180deg,#05d50b,#02b70e);--comp-iconbuttonsocial-color-background-container-telegram:linear-gradient(180deg,#2aabee,#229ed9);--comp-iconbuttonsocial-color-background-container-kakao-talk:#ffeb3b;--comp-iconbuttonsocial-color-background-container-imessage:linear-gradient(180deg,#5bf675,#0cbd2a);--comp-iconbuttonsocial-color-background-container-line:#06c755;--comp-iconbuttonsocial-color-background-container-snap:#fffc00;--comp-iconbuttonsocial-color-background-container-x-social:#000;--comp-iconbuttonsocial-color-background-container-whatsapp:#25d366;--comp-iconbuttonsocial-color-background-container-facebook:#0866ff;--comp-iconbuttonsocial-color-icon-samsung-messages:#fff;--comp-iconbuttonsocial-color-icon-discord:#e0e3ff;--comp-iconbuttonsocial-color-icon-google-messages:#0057cc;--comp-iconbuttonsocial-color-icon-snap:#fff;--comp-iconbuttonsocial-color-icon-gmail:#64656c;--comp-iconbuttonsocial-color-icon-reddit:#ff4500;--comp-iconbuttonsocial-color-icon-kakao-talk:#3e2723;--comp-iconbuttonsocial-color-icon-facebook-messenger:#0866ff;--comp-icon-size-compact-16:16px;--comp-icon-size-compact-14:14px;--comp-icon-size-compact-12:12px;--comp-icon-size-compact-10:10px;--comp-icon-size-default-32:32px;--comp-icon-size-default-24:24px;--comp-icon-size-default-20:20px;--comp-icon-size-default-16:16px;--comp-icon-size-default-14:14px;--comp-icon-size-default-12:12px;--comp-checkbox-border-width-focus-outer:2px;--comp-checkbox-border-width-focus-inner:2px;--comp-checkbox-border-width-pressed-container-error-checked:0px;--comp-checkbox-border-width-pressed-container-error-indeterminate:0px;--comp-checkbox-border-width-pressed-container-error-unchecked:2px;--comp-checkbox-border-width-pressed-container-disabled-checked:0px;--comp-checkbox-border-width-pressed-container-disabled-indeterminate:0px;--comp-checkbox-border-width-pressed-container-disabled-unchecked:0px;--comp-checkbox-border-width-pressed-container-default-checked:0px;--comp-checkbox-border-width-pressed-container-default-indeterminate:0px;--comp-checkbox-border-width-pressed-container-default-unchecked:2px;--comp-checkbox-border-width-hover-container-error-checked:0px;--comp-checkbox-border-width-hover-container-error-indeterminate:0px;--comp-checkbox-border-width-hover-container-error-unchecked:2px;--comp-checkbox-border-width-hover-container-disabled-checked:0px;--comp-checkbox-border-width-hover-container-disabled-indeterminate:0px;--comp-checkbox-border-width-hover-container-disabled-unchecked:0px;--comp-checkbox-border-width-hover-container-default-checked:0px;--comp-checkbox-border-width-hover-container-default-indeterminate:0px;--comp-checkbox-border-width-hover-container-default-unchecked:2px;--comp-checkbox-border-width-container-error-checked:0px;--comp-checkbox-border-width-container-error-indeterminate:0px;--comp-checkbox-border-width-container-error-unchecked:2px;--comp-checkbox-border-width-container-disabled-checked:0px;--comp-checkbox-border-width-container-disabled-indeterminate:0px;--comp-checkbox-border-width-container-disabled-unchecked:0px;--comp-checkbox-border-width-container-default-checked:0px;--comp-checkbox-border-width-container-default-indeterminate:0px;--comp-checkbox-border-width-container-default-unchecked:1px;--comp-buttontoggle-border-width-pressed-image-outer-enabled-subtle:1px;--comp-buttontoggle-border-width-pressed-image-outer-enabled-strong:2px;--comp-buttontoggle-border-width-pressed-image-outer-enabled-deselected:1px;--comp-buttontoggle-border-width-pressed-image-inner-enabled-subtle:1px;--comp-buttontoggle-border-width-pressed-image-inner-enabled-strong:2px;--comp-buttontoggle-border-width-pressed-image-inner-enabled-deselected:1px;--comp-buttontoggle-border-width-pressed-graphic-enabled-subtle:1px;--comp-buttontoggle-border-width-pressed-graphic-enabled-strong:0px;--comp-buttontoggle-border-width-pressed-graphic-enabled-deselected:0px;--comp-buttontoggle-border-width-pressed-save-enabled-subtle:0px;--comp-buttontoggle-border-width-pressed-save-enabled-strong:0px;--comp-buttontoggle-border-width-pressed-save-enabled-deselected:0px;--comp-buttontoggle-border-width-pressed-default-enabled-subtle:1px;--comp-buttontoggle-border-width-pressed-default-enabled-strong:0px;--comp-buttontoggle-border-width-pressed-default-enabled-deselected:0px;--comp-buttontoggle-border-width-hover-image-outer-enabled-subtle:1px;--comp-buttontoggle-border-width-hover-image-outer-enabled-strong:2px;--comp-buttontoggle-border-width-hover-image-outer-enabled-deselected:1px;--comp-buttontoggle-border-width-hover-image-inner-enabled-subtle:1px;--comp-buttontoggle-border-width-hover-image-inner-enabled-strong:2px;--comp-buttontoggle-border-width-hover-image-inner-enabled-deselected:1px;--comp-buttontoggle-border-width-hover-graphic-enabled-subtle:1px;--comp-buttontoggle-border-width-hover-graphic-enabled-strong:0px;--comp-buttontoggle-border-width-hover-graphic-enabled-deselected:0px;--comp-buttontoggle-border-width-hover-save-enabled-subtle:0px;--comp-buttontoggle-border-width-hover-save-enabled-strong:0px;--comp-buttontoggle-border-width-hover-save-enabled-deselected:0px;--comp-buttontoggle-border-width-hover-default-enabled-subtle:1px;--comp-buttontoggle-border-width-hover-default-enabled-strong:0px;--comp-buttontoggle-border-width-hover-default-enabled-deselected:0px;--comp-buttontoggle-border-width-focus-outer:2px;--comp-buttontoggle-border-width-focus-inner:2px;--comp-buttontoggle-border-width-image-outer-disabled-subtle:1px;--comp-buttontoggle-border-width-image-outer-disabled-strong:2px;--comp-buttontoggle-border-width-image-outer-disabled-deselected:0px;--comp-buttontoggle-border-width-image-outer-enabled-subtle:1px;--comp-buttontoggle-border-width-image-outer-enabled-strong:2px;--comp-buttontoggle-border-width-image-outer-enabled-deselected:0px;--comp-buttontoggle-border-width-image-inner-disabled-subtle:1px;--comp-buttontoggle-border-width-image-inner-disabled-strong:2px;--comp-buttontoggle-border-width-image-inner-disabled-deselected:0px;--comp-buttontoggle-border-width-image-inner-enabled-subtle:1px;--comp-buttontoggle-border-width-image-inner-enabled-strong:2px;--comp-buttontoggle-border-width-image-inner-enabled-deselected:0px;--comp-buttontoggle-border-width-graphic-disabled-subtle:1px;--comp-buttontoggle-border-width-graphic-disabled-strong:0px;--comp-buttontoggle-border-width-graphic-disabled-deselected:0px;--comp-buttontoggle-border-width-graphic-enabled-subtle:1px;--comp-buttontoggle-border-width-graphic-enabled-strong:0px;--comp-buttontoggle-border-width-graphic-enabled-deselected:0px;--comp-buttontoggle-border-width-save-disabled-subtle:0px;--comp-buttontoggle-border-width-save-disabled-strong:0px;--comp-buttontoggle-border-width-save-disabled-deselected:0px;--comp-buttontoggle-border-width-save-enabled-subtle:0px;--comp-buttontoggle-border-width-save-enabled-strong:0px;--comp-buttontoggle-border-width-save-enabled-deselected:0px;--comp-buttontoggle-border-width-default-disabled-subtle:1px;--comp-buttontoggle-border-width-default-disabled-strong:0px;--comp-buttontoggle-border-width-default-disabled-deselected:0px;--comp-buttontoggle-border-width-default-enabled-subtle:1px;--comp-buttontoggle-border-width-default-enabled-strong:0px;--comp-buttontoggle-border-width-default-enabled-deselected:0px;--comp-badge-border-width-focus-outer:2px;--comp-badge-border-width-focus-inner:2px;--comp-avatargroup-border-width-focus-outer:2px;--comp-avatargroup-border-width-focus-inner:2px;--comp-avatargroup-border-width-container:1px;--comp-avatar-border-width-focus-outer:2px;--comp-avatar-border-width-focus-inner:2px;--comp-avatar-border-width-container:1px;--base-motion-easing-exit:cubic-bezier(0.3,0,0.8,0.15);--base-motion-easing-enter:cubic-bezier(0.05,0.7,0.1,1);--base-motion-easing-bounce:cubic-bezier(0,0.35,0,1.25);--base-motion-easing-lateral:cubic-bezier(0.8,0,0.2,1);--base-motion-easing-expressive:cubic-bezier(0.55,0,0,1);--base-motion-easing-linear:cubic-bezier(0,0,1,1);--base-motion-duration-900:900ms;--base-motion-duration-700:700ms;--base-motion-duration-600:600ms;--base-motion-duration-500:500ms;--base-motion-duration-400:400ms;--base-motion-duration-300:300ms;--base-motion-duration-200:200ms;--base-motion-duration-150:150ms;--base-motion-duration-100:100ms;--base-motion-duration-50:50ms;--base-motion-duration-0:0ms;--base-space-unit:4px;--base-rounding-unit:4px;--base-font-textdecoration-underline:underline;--base-font-textdecoration-default:none;--base-font-letterspacing-negative-05:-0.5px;--base-font-letterspacing-negative-1:-1px;--base-font-letterspacing-05:0.5px;--base-font-letterspacing-1:1px;--base-font-letterspacing-0:0;--base-font-family-code:"SF Mono","Segoe UI Mono","Roboto Mono","Ubuntu Mono",Menlo,Consolas,Courier,monospace;--base-font-family-default-japanese:"SF Pro JP",-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol",Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",Helvetica,"ヒラギノ角ゴ Pro W3","Hiragino Kaku Gothic Pro","メイリオ",Meiryo,"ＭＳ Ｐゴシック",Arial,sans-serif;--base-font-family-default-latin:"Pin Sans",-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol",Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",Helvetica,"ヒラギノ角ゴ Pro W3","メイリオ",Meiryo,"ＭＳ Ｐゴシック",Arial,sans-serif;--base-font-size-36:36px;--base-font-size-28:28px;--base-font-size-24:24px;--base-font-size-20:20px;--base-font-size-16:16px;--base-font-size-14:14px;--base-font-size-12:12px;--base-font-weight-700:700;--base-font-weight-500:500;--base-font-weight-400:400;--base-font-lineheight-180:1.8;--base-font-lineheight-170:1.7;--base-font-lineheight-160:1.6;--base-font-lineheight-150:1.5;--base-font-lineheight-140:1.4;--base-font-lineheight-130:1.3;--base-font-lineheight-120:1.2;--base-font-lineheight-110:1.1;--base-color-pressed-orange-700:#291000;--base-color-pressed-orange-600:#612700;--base-color-pressed-orange-500:#803300;--base-color-pressed-orange-400:#c45205;--base-color-pressed-orange-300:#fe7920;--base-color-pressed-orange-200:#ff944d;--base-color-pressed-orange-100:#ffc199;--base-color-pressed-orange-50:#ffd0ad;--base-color-pressed-green-700:#05140c;--base-color-pressed-green-600:#032613;--base-color-pressed-green-500:#054221;--base-color-pressed-green-400:#045328;--base-color-pressed-green-300:#238b53;--base-color-pressed-green-200:#5bd292;--base-color-pressed-green-100:#9ee5bf;--base-color-pressed-green-50:#bcecd1;--base-color-pressed-blue-700:#0f1a52;--base-color-pressed-blue-600:#1d2f86;--base-color-pressed-blue-500:#223aaa;--base-color-pressed-blue-400:#1e3dd7;--base-color-pressed-blue-300:#5069e8;--base-color-pressed-blue-200:#617bff;--base-color-pressed-blue-100:#a8b7ff;--base-color-pressed-blue-50:#b8c2ff;--base-color-pressed-purple-700:#240029;--base-color-pressed-purple-600:#55185e;--base-color-pressed-purple-500:#6c1e76;--base-color-pressed-purple-400:#8e279b;--base-color-pressed-purple-300:#c548d6;--base-color-pressed-purple-200:#e76ff6;--base-color-pressed-purple-100:#f5adff;--base-color-pressed-purple-50:#f8b8ff;--base-color-pressed-red-700:#380000;--base-color-pressed-red-600:#600606;--base-color-pressed-red-500:#860909;--base-color-pressed-red-400:#ad0b0b;--base-color-pressed-red-300:#f50a0a;--base-color-pressed-red-200:#ff5c5c;--base-color-pressed-red-100:#ffa3a3;--base-color-pressed-red-50:#ffb8b8;--base-color-pressed-grayscale-500:#242421;--base-color-pressed-grayscale-450:#0b0b0a;--base-color-pressed-grayscale-400:#181816;--base-color-pressed-grayscale-350:#2d2d29;--base-color-pressed-grayscale-300:#474742;--base-color-pressed-grayscale-250:#5a5a54;--base-color-pressed-grayscale-200:#787873;--base-color-pressed-grayscale-150:#b0b0a6;--base-color-pressed-grayscale-100:#cecec5;--base-color-pressed-grayscale-50:#e0e0d6;--base-color-pressed-grayscale-25:#efefeb;--base-color-pressed-grayscale-0:#efefeb;--base-color-pressed-pinterest:#b2001b;--base-color-hover-orange-700:#421b00;--base-color-hover-orange-600:#7a3100;--base-color-hover-orange-500:#993d00;--base-color-hover-orange-400:#cf5606;--base-color-hover-orange-300:#fe8839;--base-color-hover-orange-200:#ffa366;--base-color-hover-orange-100:#ffd0b2;--base-color-hover-orange-50:#ffdec7;--base-color-hover-green-700:#0b2819;--base-color-hover-green-600:#053d1f;--base-color-hover-green-500:#075a2d;--base-color-hover-green-400:#056b34;--base-color-hover-green-300:#289f5f;--base-color-hover-green-200:#6fd7a0;--base-color-hover-green-100:#b3ebcd;--base-color-hover-green-50:#cff1df;--base-color-hover-blue-700:#132167;--base-color-hover-blue-600:#22379b;--base-color-hover-blue-500:#2741bf;--base-color-hover-blue-400:#2c4be2;--base-color-hover-blue-300:#5b74f0;--base-color-hover-blue-200:#7a90ff;--base-color-hover-blue-100:#c2ccff;--base-color-hover-blue-50:#d1d8ff;--base-color-hover-purple-700:#3a0042;--base-color-hover-purple-600:#681d72;--base-color-hover-purple-500:#7e238b;--base-color-hover-purple-400:#a02caf;--base-color-hover-purple-300:#cc5dda;--base-color-hover-purple-200:#eb87f7;--base-color-hover-purple-100:#f8c7ff;--base-color-hover-purple-50:#fad1ff;--base-color-hover-red-700:#520000;--base-color-hover-red-600:#780808;--base-color-hover-red-500:#9e0a0a;--base-color-hover-red-400:#c50c0c;--base-color-hover-red-300:#f72c2c;--base-color-hover-red-200:#ff7575;--base-color-hover-red-100:#ffbdbd;--base-color-hover-red-50:#ffd1d1;--base-color-hover-grayscale-500:#181816;--base-color-hover-grayscale-450:#181816;--base-color-hover-grayscale-400:#262622;--base-color-hover-grayscale-350:#3b3b36;--base-color-hover-grayscale-300:#55554f;--base-color-hover-grayscale-250:#676760;--base-color-hover-grayscale-200:#85857f;--base-color-hover-grayscale-150:#bcbcb3;--base-color-hover-grayscale-100:#dadad3;--base-color-hover-grayscale-50:#ebebe5;--base-color-hover-grayscale-25:#f6f6f3;--base-color-hover-grayscale-0:#f6f6f3;--base-color-hover-pinterest:#cc001f;--base-color-orange-700:#5c2500;--base-color-orange-600:#943b00;--base-color-orange-500:#b24700;--base-color-orange-400:#db5b06;--base-color-orange-300:#fe9752;--base-color-orange-200:#ffb380;--base-color-orange-100:#ffe0cc;--base-color-orange-50:#ffede0;--base-color-green-700:#103c25;--base-color-green-600:#07552b;--base-color-green-500:#097239;--base-color-green-400:#068440;--base-color-green-300:#2db46c;--base-color-green-200:#83ddad;--base-color-green-100:#c7f0da;--base-color-green-50:#e3f7ec;--base-color-blue-700:#17287d;--base-color-blue-600:#273eb0;--base-color-blue-500:#2b48d4;--base-color-blue-400:#435ee5;--base-color-blue-300:#677eee;--base-color-blue-200:#92a4ff;--base-color-blue-100:#dbe1ff;--base-color-blue-50:#ebeeff;--base-color-purple-700:#51005c;--base-color-purple-600:#7a2286;--base-color-purple-500:#91289f;--base-color-purple-400:#b331c4;--base-color-purple-300:#d271df;--base-color-purple-200:#ef9ff9;--base-color-purple-100:#fbdfff;--base-color-purple-50:#fdebff;--base-color-red-700:#6b0000;--base-color-red-600:#900909;--base-color-red-500:#b60c0c;--base-color-red-400:#dd0e0e;--base-color-red-300:#f84f4f;--base-color-red-200:#ff8f8f;--base-color-red-100:#ffd7d7;--base-color-red-50:#ffebeb;--base-color-grayscale-500:#000;--base-color-grayscale-450:#242421;--base-color-grayscale-400:#33332e;--base-color-grayscale-350:#494943;--base-color-grayscale-300:#62625b;--base-color-grayscale-250:#74746c;--base-color-grayscale-200:#91918c;--base-color-grayscale-150:#c8c8c1;--base-color-grayscale-100:#e5e5e0;--base-color-grayscale-50:#f6f6f3;--base-color-grayscale-25:#fbfbf9;--base-color-grayscale-0:#fff;--base-color-pinterest:#e60023;--base-color-transparent:hsla(0,0%,100%,0);--sema-motion-opacity-easing-instant:var(--base-motion-easing-linear);--sema-motion-opacity-easing-default:var(--base-motion-easing-linear);--sema-motion-opacity-duration-instant:var(--base-motion-duration-0);--sema-motion-opacity-duration-default:var(--base-motion-duration-300);--sema-motion-colorchange-easing:var(--base-motion-easing-linear);--sema-motion-colorchange-duration:var(--base-motion-duration-300);--sema-motion-scale-swipe-easing:var(--base-motion-easing-lateral);--sema-motion-scale-swipe-duration:var(--base-motion-duration-400);--sema-motion-scale-on-easing:var(--base-motion-easing-linear);--sema-motion-scale-on-duration:var(--base-motion-duration-150);--sema-motion-position-swipe-easing:var(--base-motion-easing-lateral);--sema-motion-position-swipe-duration:var(--base-motion-duration-400);--sema-motion-position-off-easing:var(--base-motion-easing-lateral);--sema-motion-position-off-duration:var(--base-motion-duration-200);--sema-motion-position-on-easing:var(--base-motion-easing-bounce);--sema-motion-position-on-duration:var(--base-motion-duration-300);--sema-motion-position-exit-easing:var(--base-motion-easing-exit);--sema-motion-position-exit-duration:var(--base-motion-duration-300);--sema-motion-position-enter-easing:var(--base-motion-easing-bounce);--sema-motion-position-enter-duration:var(--base-motion-duration-300);--sema-motion-position-fadeout-easing:var(--base-motion-easing-lateral);--sema-motion-position-fadeout-duration:var(--base-motion-duration-200);--sema-motion-position-fadein-easing:var(--base-motion-easing-lateral);--sema-motion-position-fadein-duration:var(--base-motion-duration-300);--sema-font-textdecoration-compact-100-emphasis:var( --base-font-textdecoration-default );--sema-font-textdecoration-compact-100-link:var( --base-font-textdecoration-underline );--sema-font-textdecoration-compact-100-default:var( --base-font-textdecoration-default );--sema-font-textdecoration-body-400-emphasis:var( --base-font-textdecoration-default );--sema-font-textdecoration-body-400-link:var( --base-font-textdecoration-underline );--sema-font-textdecoration-body-400-default:var( --base-font-textdecoration-default );--sema-font-textdecoration-body-300-emphasis:var( --base-font-textdecoration-default );--sema-font-textdecoration-body-300-link:var( --base-font-textdecoration-underline );--sema-font-textdecoration-body-300-default:var( --base-font-textdecoration-default );--sema-font-textdecoration-body-200-emphasis:var( --base-font-textdecoration-default );--sema-font-textdecoration-body-200-link:var( --base-font-textdecoration-underline );--sema-font-textdecoration-body-200-default:var( --base-font-textdecoration-default );--sema-font-textdecoration-body-100-emphasis:var( --base-font-textdecoration-default );--sema-font-textdecoration-body-100-link:var( --base-font-textdecoration-underline );--sema-font-textdecoration-body-100-default:var( --base-font-textdecoration-default );--sema-font-textdecoration-ui-400:var(--base-font-textdecoration-default);--sema-font-textdecoration-ui-300:var(--base-font-textdecoration-default);--sema-font-textdecoration-ui-200:var(--base-font-textdecoration-default);--sema-font-textdecoration-ui-100:var(--base-font-textdecoration-default);--sema-font-textdecoration-heading-700:var( --base-font-textdecoration-default );--sema-font-textdecoration-heading-600:var( --base-font-textdecoration-default );--sema-font-textdecoration-heading-500:var( --base-font-textdecoration-default );--sema-font-textdecoration-heading-400:var( --base-font-textdecoration-default );--sema-font-textdecoration-heading-300:var( --base-font-textdecoration-default );--sema-font-textdecoration-heading-200:var( --base-font-textdecoration-default );--sema-font-letterspacing-compact-100:var(--base-font-letterspacing-0);--sema-font-letterspacing-body-400:var(--base-font-letterspacing-0);--sema-font-letterspacing-body-300:var(--base-font-letterspacing-0);--sema-font-letterspacing-body-200:var(--base-font-letterspacing-0);--sema-font-letterspacing-body-100:var(--base-font-letterspacing-0);--sema-font-letterspacing-ui-400:var(--base-font-letterspacing-0);--sema-font-letterspacing-ui-300:var(--base-font-letterspacing-0);--sema-font-letterspacing-ui-200:var(--base-font-letterspacing-0);--sema-font-letterspacing-ui-100:var(--base-font-letterspacing-0);--sema-font-letterspacing-heading-700:var( --base-font-letterspacing-negative-05 );--sema-font-letterspacing-heading-600:var( --base-font-letterspacing-negative-05 );--sema-font-letterspacing-heading-500:var( --base-font-letterspacing-negative-05 );--sema-font-letterspacing-heading-400:var(--base-font-letterspacing-0);--sema-font-letterspacing-heading-300:var(--base-font-letterspacing-0);--sema-font-letterspacing-heading-200:var(--base-font-letterspacing-0);--sema-font-lineheight-xs:var(--base-font-lineheight-110);--sema-font-lineheight-sm:var(--base-font-lineheight-120);--sema-font-lineheight-md:var(--base-font-lineheight-130);--sema-font-lineheight-lg:var(--base-font-lineheight-140);--sema-font-lineheight-xl:var(--base-font-lineheight-150);--sema-font-lineheight-compact-100:var(--base-font-lineheight-120);--sema-font-lineheight-body-400:var(--base-font-lineheight-140);--sema-font-lineheight-body-300:var(--base-font-lineheight-140);--sema-font-lineheight-body-200:var(--base-font-lineheight-140);--sema-font-lineheight-body-100:var(--base-font-lineheight-150);--sema-font-lineheight-ui-400:var(--base-font-lineheight-140);--sema-font-lineheight-ui-300:var(--base-font-lineheight-140);--sema-font-lineheight-ui-200:var(--base-font-lineheight-140);--sema-font-lineheight-ui-100:var(--base-font-lineheight-150);--sema-font-lineheight-heading-700:var(--base-font-lineheight-110);--sema-font-lineheight-heading-600:var(--base-font-lineheight-110);--sema-font-lineheight-heading-500:var(--base-font-lineheight-110);--sema-font-lineheight-heading-400:var(--base-font-lineheight-120);--sema-font-lineheight-heading-300:var(--base-font-lineheight-140);--sema-font-lineheight-heading-200:var(--base-font-lineheight-140);--sema-font-family-compact-100:var(--base-font-family-default-latin);--sema-font-family-body-400:var(--base-font-family-default-latin);--sema-font-family-body-300:var(--base-font-family-default-latin);--sema-font-family-body-200:var(--base-font-family-default-latin);--sema-font-family-body-100:var(--base-font-family-default-latin);--sema-font-family-ui-400:var(--base-font-family-default-latin);--sema-font-family-ui-300:var(--base-font-family-default-latin);--sema-font-family-ui-200:var(--base-font-family-default-latin);--sema-font-family-ui-100:var(--base-font-family-default-latin);--sema-font-family-heading-700:var(--base-font-family-default-latin);--sema-font-family-heading-600:var(--base-font-family-default-latin);--sema-font-family-heading-500:var(--base-font-family-default-latin);--sema-font-family-heading-400:var(--base-font-family-default-latin);--sema-font-family-heading-300:var(--base-font-family-default-latin);--sema-font-family-heading-200:var(--base-font-family-default-latin);--sema-font-size-compact-100:var(--base-font-size-12);--sema-font-size-body-400:var(--base-font-size-20);--sema-font-size-body-300:var(--base-font-size-16);--sema-font-size-body-200:var(--base-font-size-14);--sema-font-size-body-100:var(--base-font-size-12);--sema-font-size-ui-400:var(--base-font-size-20);--sema-font-size-ui-300:var(--base-font-size-16);--sema-font-size-ui-200:var(--base-font-size-14);--sema-font-size-ui-100:var(--base-font-size-12);--sema-font-size-heading-700:var(--base-font-size-36);--sema-font-size-heading-600:var(--base-font-size-28);--sema-font-size-heading-500:var(--base-font-size-24);--sema-font-size-heading-400:var(--base-font-size-20);--sema-font-size-heading-300:var(--base-font-size-16);--sema-font-size-heading-200:var(--base-font-size-14);--sema-font-weight-compact-100-emphasis:var(--base-font-weight-700);--sema-font-weight-compact-100-default:var(--base-font-weight-400);--sema-font-weight-body-400-emphasis:var(--base-font-weight-700);--sema-font-weight-body-400-default:var(--base-font-weight-400);--sema-font-weight-body-300-emphasis:var(--base-font-weight-700);--sema-font-weight-body-300-default:var(--base-font-weight-400);--sema-font-weight-body-200-emphasis:var(--base-font-weight-700);--sema-font-weight-body-200-default:var(--base-font-weight-400);--sema-font-weight-body-100-emphasis:var(--base-font-weight-700);--sema-font-weight-body-100-default:var(--base-font-weight-400);--sema-font-weight-ui-400:var(--base-font-weight-500);--sema-font-weight-ui-300:var(--base-font-weight-500);--sema-font-weight-ui-200:var(--base-font-weight-500);--sema-font-weight-ui-100:var(--base-font-weight-500);--sema-font-weight-heading-700:var(--base-font-weight-700);--sema-font-weight-heading-600:var(--base-font-weight-700);--sema-font-weight-heading-500:var(--base-font-weight-700);--sema-font-weight-heading-400:var(--base-font-weight-700);--sema-font-weight-heading-300:var(--base-font-weight-700);--sema-font-weight-heading-200:var(--base-font-weight-700);--sema-color-pressed-icon-verified-merchant:var( --base-color-pressed-blue-400 );--sema-color-pressed-icon-verified-pinner:var( --base-color-pressed-pinterest );--sema-color-pressed-icon-dark:var(--base-color-pressed-grayscale-500);--sema-color-pressed-icon-light:var(--base-color-pressed-grayscale-0);--sema-color-pressed-icon-inverse:var(--base-color-pressed-grayscale-0);--sema-color-pressed-icon-error:var(--base-color-pressed-red-400);--sema-color-pressed-icon-warning:var(--base-color-pressed-orange-400);--sema-color-pressed-icon-success:var(--base-color-pressed-green-400);--sema-color-pressed-icon-recommendation:var( --base-color-pressed-purple-400 );--sema-color-pressed-icon-info:var(--base-color-pressed-blue-400);--sema-color-pressed-icon-primary:var(--base-color-pressed-pinterest);--sema-color-pressed-icon-link:var(--base-color-pressed-blue-500);--sema-color-pressed-icon-subtle:var(--base-color-pressed-grayscale-300);--sema-color-pressed-icon-neutral:var(--base-color-pressed-grayscale-300);--sema-color-pressed-icon-default:var(--base-color-pressed-grayscale-500);--sema-color-pressed-text-dark:var(--base-color-pressed-grayscale-500);--sema-color-pressed-text-light:var(--base-color-pressed-grayscale-0);--sema-color-pressed-text-inverse:var(--base-color-pressed-grayscale-0);--sema-color-pressed-text-error:var(--base-color-pressed-red-500);--sema-color-pressed-text-warning:var(--base-color-pressed-orange-500);--sema-color-pressed-text-success:var(--base-color-pressed-green-500);--sema-color-pressed-text-recommendation:var( --base-color-pressed-purple-500 );--sema-color-pressed-text-info:var(--base-color-pressed-blue-500);--sema-color-pressed-text-primary:var(--base-color-pressed-pinterest);--sema-color-pressed-text-link:var(--base-color-pressed-blue-500);--sema-color-pressed-text-subtle:var(--base-color-pressed-grayscale-300);--sema-color-pressed-text-neutral:var(--base-color-pressed-grayscale-350);--sema-color-pressed-text-default:var(--base-color-pressed-grayscale-500);--sema-color-pressed-border-dark-interactive:var( --base-color-pressed-grayscale-200 );--sema-color-pressed-border-dark-decorative:var( --base-color-pressed-grayscale-350 );--sema-color-pressed-border-light-interactive:var( --base-color-pressed-grayscale-200 );--sema-color-pressed-border-light-decorative:var( --base-color-pressed-grayscale-150 );--sema-color-pressed-border-inverse:var(--base-color-pressed-grayscale-0);--sema-color-pressed-border-education:var(--base-color-pressed-blue-400);--sema-color-pressed-border-error:var(--base-color-pressed-red-400);--sema-color-pressed-border-success:var(--base-color-pressed-green-400);--sema-color-pressed-border-selected:var(--base-color-pressed-grayscale-400);--sema-color-pressed-border-interactive:var( --base-color-pressed-grayscale-200 );--sema-color-pressed-border-decorative:var( --base-color-pressed-grayscale-150 );--sema-color-pressed-background-error-weak:var(--base-color-pressed-red-50);--sema-color-pressed-background-error-default:var( --base-color-pressed-red-500 );--sema-color-pressed-background-warning-weak:var( --base-color-pressed-orange-50 );--sema-color-pressed-background-warning-default:var( --base-color-pressed-orange-500 );--sema-color-pressed-background-success-weak:var( --base-color-pressed-green-50 );--sema-color-pressed-background-success-default:var( --base-color-pressed-green-500 );--sema-color-pressed-background-recommendation-weak:var( --base-color-pressed-purple-50 );--sema-color-pressed-background-recommendation-default:var( --base-color-pressed-purple-500 );--sema-color-pressed-background-neutral-weak:var( --base-color-pressed-grayscale-50 );--sema-color-pressed-background-neutral-default:var( --base-color-pressed-grayscale-350 );--sema-color-pressed-background-info-weak:var(--base-color-pressed-blue-50);--sema-color-pressed-background-info-default:var( --base-color-pressed-blue-400 );--sema-color-pressed-background-dark:var(--base-color-pressed-grayscale-500);--sema-color-pressed-background-light:var(--base-color-pressed-grayscale-0);--sema-color-pressed-background-inverse:var( --base-color-pressed-grayscale-500 );--sema-color-pressed-background-scrim:var(--base-color-pressed-grayscale-50);--sema-color-pressed-background-elevation:var( --base-color-pressed-grayscale-0 );--sema-color-pressed-background-education:var(--base-color-pressed-blue-400);--sema-color-pressed-background-checked:var(--base-color-pressed-blue-400);--sema-color-pressed-background-selected:var( --base-color-pressed-grayscale-400 );--sema-color-pressed-background-subtle:var( --base-color-pressed-grayscale-50 );--sema-color-pressed-background-tertiary:var( --base-color-pressed-grayscale-250 );--sema-color-pressed-background-secondary:var( --base-color-pressed-grayscale-100 );--sema-color-pressed-background-primary:var(--base-color-pressed-pinterest);--sema-color-pressed-background-default:var( --base-color-pressed-grayscale-0 );--sema-color-hover-icon-verified-merchant:var(--base-color-hover-blue-400);--sema-color-hover-icon-verified-pinner:var(--base-color-hover-pinterest);--sema-color-hover-icon-dark:var(--base-color-hover-grayscale-500);--sema-color-hover-icon-light:var(--base-color-hover-grayscale-0);--sema-color-hover-icon-inverse:var(--base-color-hover-grayscale-0);--sema-color-hover-icon-error:var(--base-color-hover-red-400);--sema-color-hover-icon-warning:var(--base-color-hover-orange-400);--sema-color-hover-icon-success:var(--base-color-hover-green-400);--sema-color-hover-icon-recommendation:var(--base-color-hover-purple-400);--sema-color-hover-icon-info:var(--base-color-hover-blue-400);--sema-color-hover-icon-primary:var(--base-color-hover-pinterest);--sema-color-hover-icon-link:var(--base-color-hover-blue-500);--sema-color-hover-icon-subtle:var(--base-color-hover-grayscale-300);--sema-color-hover-icon-neutral:var(--base-color-hover-grayscale-300);--sema-color-hover-icon-default:var(--base-color-hover-grayscale-500);--sema-color-hover-text-dark:var(--base-color-hover-grayscale-500);--sema-color-hover-text-light:var(--base-color-hover-grayscale-0);--sema-color-hover-text-inverse:var(--base-color-hover-grayscale-0);--sema-color-hover-text-error:var(--base-color-hover-red-500);--sema-color-hover-text-warning:var(--base-color-hover-orange-500);--sema-color-hover-text-success:var(--base-color-hover-green-500);--sema-color-hover-text-recommendation:var(--base-color-hover-purple-500);--sema-color-hover-text-info:var(--base-color-hover-blue-500);--sema-color-hover-text-primary:var(--base-color-hover-pinterest);--sema-color-hover-text-link:var(--base-color-hover-blue-500);--sema-color-hover-text-subtle:var(--base-color-hover-grayscale-300);--sema-color-hover-text-neutral:var(--base-color-hover-grayscale-350);--sema-color-hover-text-default:var(--base-color-hover-grayscale-500);--sema-color-hover-border-dark-interactive:var( --base-color-hover-grayscale-200 );--sema-color-hover-border-dark-decorative:var( --base-color-hover-grayscale-350 );--sema-color-hover-border-light-interactive:var( --base-color-hover-grayscale-200 );--sema-color-hover-border-light-decorative:var( --base-color-hover-grayscale-150 );--sema-color-hover-border-inverse:var(--base-color-hover-grayscale-0);--sema-color-hover-border-education:var(--base-color-hover-blue-400);--sema-color-hover-border-error:var(--base-color-hover-red-400);--sema-color-hover-border-success:var(--base-color-hover-green-400);--sema-color-hover-border-selected:var(--base-color-hover-grayscale-400);--sema-color-hover-border-interactive:var(--base-color-hover-grayscale-200);--sema-color-hover-border-decorative:var(--base-color-hover-grayscale-150);--sema-color-hover-background-error-weak:var(--base-color-hover-red-50);--sema-color-hover-background-error-default:var(--base-color-hover-red-500);--sema-color-hover-background-warning-weak:var(--base-color-hover-orange-50);--sema-color-hover-background-warning-default:var( --base-color-hover-orange-500 );--sema-color-hover-background-success-weak:var(--base-color-hover-green-50);--sema-color-hover-background-success-default:var( --base-color-hover-green-500 );--sema-color-hover-background-recommendation-weak:var( --base-color-hover-purple-50 );--sema-color-hover-background-recommendation-default:var( --base-color-hover-purple-500 );--sema-color-hover-background-neutral-weak:var( --base-color-hover-grayscale-50 );--sema-color-hover-background-neutral-default:var( --base-color-hover-grayscale-350 );--sema-color-hover-background-info-weak:var(--base-color-hover-blue-50);--sema-color-hover-background-info-default:var(--base-color-hover-blue-400);--sema-color-hover-background-dark:var(--base-color-hover-grayscale-500);--sema-color-hover-background-light:var(--base-color-hover-grayscale-0);--sema-color-hover-background-inverse:var(--base-color-hover-grayscale-500);--sema-color-hover-background-scrim:var(--base-color-hover-grayscale-50);--sema-color-hover-background-elevation:var(--base-color-hover-grayscale-0);--sema-color-hover-background-education:var(--base-color-hover-blue-400);--sema-color-hover-background-checked:var(--base-color-hover-blue-400);--sema-color-hover-background-selected:var(--base-color-hover-grayscale-400);--sema-color-hover-background-subtle:var(--base-color-hover-grayscale-50);--sema-color-hover-background-tertiary:var(--base-color-hover-grayscale-250);--sema-color-hover-background-secondary:var( --base-color-hover-grayscale-100 );--sema-color-hover-background-primary:var(--base-color-hover-pinterest);--sema-color-hover-background-default:var(--base-color-hover-grayscale-0);--sema-color-icon-verified-merchant:var(--base-color-blue-400);--sema-color-icon-verified-pinner:var(--base-color-pinterest);--sema-color-icon-disabled:var(--base-color-grayscale-200);--sema-color-icon-dark:var(--base-color-grayscale-500);--sema-color-icon-light:var(--base-color-grayscale-0);--sema-color-icon-inverse:var(--base-color-grayscale-0);--sema-color-icon-error:var(--base-color-red-400);--sema-color-icon-warning:var(--base-color-orange-400);--sema-color-icon-success:var(--base-color-green-400);--sema-color-icon-recommendation:var(--base-color-purple-400);--sema-color-icon-info:var(--base-color-blue-400);--sema-color-icon-primary:var(--base-color-pinterest);--sema-color-icon-link:var(--base-color-blue-500);--sema-color-icon-subtle:var(--base-color-grayscale-300);--sema-color-icon-neutral:var(--base-color-grayscale-300);--sema-color-icon-default:var(--base-color-grayscale-500);--sema-color-text-disabled:var(--base-color-grayscale-200);--sema-color-text-dark:var(--base-color-grayscale-500);--sema-color-text-light:var(--base-color-grayscale-0);--sema-color-text-inverse:var(--base-color-grayscale-0);--sema-color-text-error:var(--base-color-red-500);--sema-color-text-warning:var(--base-color-orange-500);--sema-color-text-success:var(--base-color-green-500);--sema-color-text-recommendation:var(--base-color-purple-500);--sema-color-text-info:var(--base-color-blue-500);--sema-color-text-primary:var(--base-color-pinterest);--sema-color-text-link:var(--base-color-blue-500);--sema-color-text-subtle:var(--base-color-grayscale-300);--sema-color-text-neutral:var(--base-color-grayscale-350);--sema-color-text-default:var(--base-color-grayscale-500);--sema-color-border-focus-inner-light:var(--base-color-grayscale-0);--sema-color-border-focus-inner-dark:var(--base-color-grayscale-500);--sema-color-border-focus-inner-inverse:var(--base-color-grayscale-500);--sema-color-border-focus-inner-default:var(--base-color-grayscale-0);--sema-color-border-focus-outer-light:var(--base-color-blue-200);--sema-color-border-focus-outer-dark:var(--base-color-blue-400);--sema-color-border-focus-outer-inverse:var(--base-color-blue-200);--sema-color-border-focus-outer-default:var(--base-color-blue-400);--sema-color-border-dark-interactive:var(--base-color-grayscale-200);--sema-color-border-dark-decorative:var(--base-color-grayscale-350);--sema-color-border-light-interactive:var(--base-color-grayscale-200);--sema-color-border-light-decorative:var(--base-color-grayscale-150);--sema-color-border-transparent:var(--base-color-transparent);--sema-color-border-inverse:var(--base-color-grayscale-0);--sema-color-border-education:var(--base-color-blue-400);--sema-color-border-error:var(--base-color-red-400);--sema-color-border-success:var(--base-color-green-400);--sema-color-border-disabled:var(--base-color-grayscale-150);--sema-color-border-selected:var(--base-color-grayscale-400);--sema-color-border-interactive:var(--base-color-grayscale-200);--sema-color-border-decorative:var(--base-color-grayscale-150);--sema-color-background-error-weak:var(--base-color-red-50);--sema-color-background-error-default:var(--base-color-red-500);--sema-color-background-warning-weak:var(--base-color-orange-50);--sema-color-background-warning-default:var(--base-color-orange-500);--sema-color-background-success-weak:var(--base-color-green-50);--sema-color-background-success-default:var(--base-color-green-500);--sema-color-background-recommendation-weak:var(--base-color-purple-50);--sema-color-background-recommendation-default:var(--base-color-purple-500);--sema-color-background-neutral-weak:var(--base-color-grayscale-50);--sema-color-background-neutral-default:var(--base-color-grayscale-350);--sema-color-background-info-weak:var(--base-color-blue-50);--sema-color-background-info-default:var(--base-color-blue-400);--sema-color-background-disabled:var(--base-color-grayscale-100);--sema-color-background-dark:var(--base-color-grayscale-500);--sema-color-background-light:var(--base-color-grayscale-0);--sema-color-background-inverse:var(--base-color-grayscale-500);--sema-color-background-scrim:var(--base-color-grayscale-50);--sema-color-background-elevation:var(--base-color-grayscale-0);--sema-color-background-education:var(--base-color-blue-400);--sema-color-background-checked:var(--base-color-blue-400);--sema-color-background-selected:var(--base-color-grayscale-400);--sema-color-background-subtle:var(--base-color-grayscale-50);--sema-color-background-tertiary:var(--base-color-grayscale-250);--sema-color-background-secondary:var(--base-color-grayscale-100);--sema-color-background-primary:var(--base-color-pinterest);--sema-color-background-default:var(--base-color-grayscale-0);--comp-segmentedcontrol-color-pressed-background-segment-deselected:var( --sema-color-background-transparent );--comp-segmentedcontrol-color-hover-background-segment-deselected:var( --sema-color-background-transparent );--comp-segmentedcontrol-color-background-segment-deselected:var( --sema-color-background-transparent );--comp-bannerupsell-border-width-container-default:var(--sema-space-0);--comp-bannerupsell-color-background-graphic-container:var( --sema-color-background-transparent );--comp-bannerslim-border-width-container-recommendation-compact:var( --sema-space-0 );--comp-bannerslim-border-width-container-recommendation-expanded:var( --sema-space-0 );--comp-bannerslim-border-width-container-error-compact:var(--sema-space-0);--comp-bannerslim-border-width-container-error-expanded:var(--sema-space-0);--comp-bannerslim-border-width-container-warning-compact:var(--sema-space-0);--comp-bannerslim-border-width-container-warning-expanded:var( --sema-space-0 );--comp-bannerslim-border-width-container-success-compact:var(--sema-space-0);--comp-bannerslim-border-width-container-success-expanded:var( --sema-space-0 );--comp-bannerslim-border-width-container-info-compact:var(--sema-space-0);--comp-bannerslim-border-width-container-info-expanded:var(--sema-space-0);--comp-bannerslim-border-width-container-neutral-compact:var(--sema-space-0);--comp-bannerslim-border-width-container-neutral-expanded:var( --sema-space-0 );--comp-bannerslim-border-width-container-default-compact:var(--sema-space-0);--comp-bannerslim-border-width-container-default-expanded:var( --sema-space-0 );--comp-bannerslim-color-background-recommendation-compact:var( --sema-color-background-transparent );--comp-bannerslim-color-background-error-compact:var( --sema-color-background-transparent );--comp-bannerslim-color-background-warning-compact:var( --sema-color-background-transparent );--comp-bannerslim-color-background-success-compact:var( --sema-color-background-transparent );--comp-bannerslim-color-background-info-compact:var( --sema-color-background-transparent );--comp-bannerslim-color-background-neutral-compact:var( --sema-color-background-transparent );--comp-bannerslim-color-background-default-compact:var( --sema-color-background-transparent );--comp-bannercallout-border-width-container-recommendation:var( --sema-space-0 );--comp-bannercallout-border-width-container-error:var(--sema-space-0);--comp-bannercallout-border-width-container-warning:var(--sema-space-0);--comp-bannercallout-border-width-container-success:var(--sema-space-0);--comp-bannercallout-border-width-container-info:var(--sema-space-0);--comp-bannercallout-border-width-container-neutral:var(--sema-space-0);--comp-bannercallout-border-width-container-default:var(--sema-space-0);--comp-tab-color-pressed-background-container-selected:var( --sema-color-background-transparent );--comp-tab-color-hover-background-container-selected:var( --sema-color-background-transparent );--comp-tab-color-background-underline-deselected:var( --sema-color-background-transparent );--comp-tab-color-background-container-disabled:var( --sema-color-background-transparent );--comp-tab-color-background-container-selected:var( --sema-color-background-transparent );--comp-tab-color-background-container-deselected:var( --sema-color-background-transparent );--comp-switch-color-pressed-background-container-enabled-on:var( --base-color-pressed-blue-400 );--comp-switch-color-pressed-background-container-enabled-off:var( --base-color-pressed-grayscale-200 );--comp-switch-color-hover-background-container-enabled-on:var( --base-color-hov | 2026-01-13T09:29:41 |
https://www.linkedin.com/uas/login?session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fposts%2Fverified-first_hrcalendar-humanresources-2026planning-activity-7414704371352915968-FF65&trk=public_post_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=POST&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:41 |
https://support.smartbear.com/reflect/docs/en/integrations.html#in-this-section-2110472 | Integrations | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Integrations Integrations Learn how to integrate Reflect into your existing development and/or testing workflows. In This Section Email Notifications Get automated alerts when tests start failing. Issue Trackers Create bug tickets for failing tests directly from Reflect. Continuous Integration (CI/CD) Automatically execute Reflect tests from within your Continuous Integration/Continuous Deployment pipeline. Slack Send automatic notifications to a Slack channel of your choice when tests fail. GitHub Connect to GitHub to allow Reflect to run tests on every Pull Request and mark PRs as passing/failing. Test Case Management Automatically sync Reflect tests and test results to your existing Test Case Management tool In this section : Integrations In This Section Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:41 |
https://git-scm.com/book/bg/v2/%d0%9a%d0%bb%d0%be%d0%bd%d0%be%d0%b2%d0%b5-%d0%b2-Git-%d0%9e%d1%82%d0%b4%d0%b0%d0%bb%d0%b5%d1%87%d0%b5%d0%bd%d0%b8-%d0%ba%d0%bb%d0%be%d0%bd%d0%be%d0%b2%d0%b5 | Git - Отдалечени клонове About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 3.5 Клонове в Git - Отдалечени клонове Отдалечени клонове Отдалечените референции са указатели към вашите отдалечени хранилища, вкл. клонове, тагове и др. Можете да получите списък на всички отдалечени указатели изрично с командата git ls-remote <remote> , или git remote show <remote> за отдалечени клонове и друга информация. Най-използваната функционалност от разработчиците е да се възползват от предимствата на remote-tracking клоновете. Remote-tracking клоновете са указатели към състоянието на отдалечените клонове код. Това са локални референции, които не можете да местите, те се преместват автоматично за вас в резултат от някакви мрежови комуникации, така че да е сигурно, че те акуратно отразяват статуса на отдалеченото хранилище. Служат като отметки за да ви напомнят в какво състояние са били отдалечените клонове код последния път, когато сте се свързвали с тях. Те следват конвенцията <remote>/<branch> . Например, ако искате да видите в какво състояние е бил master клона на вашето отдалечено хранилище origin последния път, когато сте комуникирали с него, можете да го направите посредством клона origin/master . Ако съвместно с ваш колега работите по даден проблем и той е публикувал нещо в клона iss53 , вие можете да имате локален такъв със същото име, но клонът на сървъра ще е достъпен през референцията origin/iss53 . Това може да е объркващо, така че нека го разгледаме с пример. Нека кажем, че имате Git сървър в мрежата ви на адрес git.ourcompany.com . Ако клонирате хранилище от него, clone командата на Git автоматично ще го именува с името origin , ще издърпва всички данни от него, ще създаде указател към мястото където е master клона на това хранилище и ще го съхрани като origin/master локално при вас. Git също така създава локален master клон, който сочи към същото място в проекта, така че да имате от къде да започнете локалната си работа. Забележка “origin” не е специална дума Точно както и master - думата origin няма никакво специално значение в Git. Докато “master” е името по подразбиране за началния клон когато изпълните git init , то “origin” се ползва по подразбиране, когато изпълнявате git clone . Това е единствената причина за толкова разпространеното ползване на тези две думи. Ако изпълните git clone -o booyah вместо просто git clone , тогава ще имате booyah/master като ваш отдалечен клон по подразбиране. Фигура 30. Сървърното и локалното хранилище след клониране Ако вие вършите някаква работа в локалния си master клон и междувременно някой друг изпрати нещо към git.ourcompany.com и промени master клона там, тогава вашите истории на промените ще се движат напред по различни начини. Също така, докато не контакувате с вашия origin сървър, указателят origin/master не се премества самичък. Фигура 31. Локалната и отдалечената работа могат да се разделят За да синхронизирате работата си така, че да отразява промените на сървъра, използвайте командата git fetch <remote> (в нашия случай git fetch origin ). Тази команда установява кой е адреса на сървъра “origin” (в случая git.ourcompany.com ), издърпва всички данни, които все още нямате локално и обновява локалната база данни, така че указателят origin/master вече да сочи към нова, по-актуална позиция от историята. Фигура 32. git fetch обновява отдалечените ви референции За да демонстрираме какво е да имате много отдалечени сървъри и как изглеждат клоновете на съответните отдалечени проекти, нека приемем, че имате още един вътрешнофирмен Git сървър, който се използва само за разработка от някой от вашите sprint екипи. Сървърът е на адрес git.team1.ourcompany.com . Можете да го добавите като нова отдалечена референция към проекта, в който работите, с командата git remote add , която разгледахме в Основи на Git . Наречете това отдалечено хранилище teamone , което ще е краткото име за целия URL. Фигура 33. Добавяне на нов remote Сега можете да изпълните git fetch teamone за да изтеглите всичко, което този сървър има, а вие все още нямате локално. Понеже този сървър съхранява подмножество от данните на вашия origin сървър, Git всъщност не тегли от него нищо, а просто създава remote-tracking клон наречен teamone/master , който сочи към последния къмит, който teamone има за своя master клон. Фигура 34. Remote tracking клон за teamone/master Изпращане към сървъра (pushing) Когато искате да споделите работата от ваш локален клон с другите си колеги, трябва да го изпратите към отдалечено хранилище, към което имате права за писане. Вашите локални клонове не се синхронизират автоматично с регистрираните отдалечени хранилища — вие трябва изрично да ги изпратите към тях. По този начин, можете да си имате частни клонове код само за вас и които не желаете да споделяте, а да споделяте само topic клоновете, към които допринасяте. Ако имате клон наречен serverfix , който искате да споделите с другите, можете да го изпратите по същия начин, по който изпратихте първия си клон. Изпълнете git push <remote> <branch> : $ git push origin serverfix Counting objects: 24, done. Delta compression using up to 8 threads. Compressing objects: 100% (15/15), done. Writing objects: 100% (24/24), 1.91 KiB | 0 bytes/s, done. Total 24 (delta 2), reused 0 (delta 0) To https://github.com/schacon/simplegit * [new branch] serverfix -> serverfix Това е един вид съкращение. Git автоматично разширява името на клона serverfix до refs/heads/serverfix:refs/heads/serverfix , което означава, “Вземи локалния ми клон serverfix и го изпрати към отдалеченото хранилище, обновявайки отдалечения клон serverfix”. Ще разгледаме частта refs/heads/ в подробности в Git на ниско ниво , засега не ѝ обръщайте внимание. Можете също да изпълните git push origin serverfix:serverfix , което върши същата работа, тази команда означава “Вземи локалния ми клон serverfix и го слей с отдалечения със същото име”. Можете да използвате този формат, за да слеете локален клон с отдалечен, който се казва по различен начин. Ако не желаете отдалеченият да се казва serverfix в сървърното хранилище, можете да изпълните например git push origin serverfix:awesomebranch и отдалечения клон ще се казва awesomebranch . Забележка Не пишете паролата си всеки път Ако използвате HTTPS URL за изпращане, Git сървърът ще ви пита за име и парола всеки път когато изпращате към него. По подразбиране ще получите запитване в терминала, така че сървърът да знае дали можете да записвате на него Ако не желаете това, можете да направите т. нар. “credential cache”. Най-лесно е да запомните паролата в кеша за известно време, което можете да направите с командата git config --global credential.helper cache . За повече информация за различните опции за този кеш, вижте Credential Storage система . Следващият път, когато колегите ви теглят от сървъра, ще получат референция към точката в която сочи сървърната версия на клона serverfix под формата на отдалечен за тях клон origin/serverfix : $ git fetch origin remote: Counting objects: 7, done. remote: Compressing objects: 100% (2/2), done. remote: Total 3 (delta 0), reused 3 (delta 0) Unpacking objects: 100% (3/3), done. From https://github.com/schacon/simplegit * [new branch] serverfix -> origin/serverfix Важно е да се запомни, че когато изпълните git fetch за да изтеглите новосъздадени remote-tracking клонове, вие не получавате автоматично техни редактируеми копия! С други думи, в този случай няма да имате действителното съдържание на клона serverfix , а само указателят origin/serverfix , който не можете да променяте. За да стане това, трябва да го слеете в текущия си клон с git merge origin/serverfix . Ако не желаете това да стане в текущия клон, а в нов локален такъв с име serverfix , можете да го базирате на remote-tracking клона: $ git checkout -b serverfix origin/serverfix Branch serverfix set up to track remote branch serverfix from origin. Switched to a new branch 'serverfix' Това ви дава локален клон, в който да работите и който стартира от точката, в която е origin/serverfix . Проследяване на клонове Извличането на локален клон от remote-tracking такъв автоматично създава т. нар. “tracking branch” (и клонът, който той следи се нарича “upstream branch”). Проследяващите клонове са локални такива, които имат директна връзка с отдалечен клон. Ако сте в такъв проследяващ клон и изпълните git pull , Git автоматично знае кой сървър да ползва за изтегляне и в кой клон да слее разликите. Когато клонирате хранилище, системата създава автоматично master клон, който проследява origin/master . Обаче, ако желаете, можете да създадете и други проследяващи клонове - такива, които следят клонове от други отдалечени хранилища или пък не следят точно master клона от сървъра. Прост случай е примерът, който току що видяхте, изпълнявайки git checkout -b <branch> <remote>/<branch> . Това е често случваща се операция, за която Git осигурява --track съкращение: $ git checkout --track origin/serverfix Branch serverfix set up to track remote branch serverfix from origin. Switched to a new branch 'serverfix' В действителност, това е толкова често срещано, че съществува съкращение на съкратената версия. Ако клонът с името, към който се опитвате да превключите, не съществува локално, но съвпада по име с такъв от точно едно отдалечено хранилище, Git ще създаде проследяващ клон за вас: $ git checkout serverfix Branch serverfix set up to track remote branch serverfix from origin. Switched to a new branch 'serverfix' Ако искате да създадете клон с различно име от това, което е в отдалеченото хранилище, можете лесно да ползвате първата версия с различно име за локалния клон: $ git checkout -b sf origin/serverfix Branch sf set up to track remote branch serverfix from origin. Switched to a new branch 'sf' Сега, локалният ви клон sf автоматично ще тегли от origin/serverfix . Ако ли пък имате локален клон и искате да го накарате да следи клона, който току що изтеглихте, или пък искате да смените upstream клона, можете да използвате -u или --set-upstream-to опциите на git branch за да укажете изрично името. $ git branch -u origin/serverfix Branch serverfix set up to track remote branch serverfix from origin. Забележка Upstream съкращение Когато имате настроен проследяващ клон, можете да се обръщате към неговия upstream клон със съкращенията @{upstream} или @{u} . Така, ако сте на master клона и той следи origin/master , можете да използвате git merge @{u} вместо git merge origin/master , ако ви е по-удобно. За да отпечатате какви проследявани клонове имате, използвайте параметъра -vv на git branch . Това ще изведе списък с локалните клонове с повече информация, вкл. какво следи всеки клон и дали той е напред/назад или и двете в сравнение с локалната версия. $ git branch -vv iss53 7e424c3 [origin/iss53: ahead 2] Add forgotten brackets master 1ae2a45 [origin/master] Deploy index fix * serverfix f8674d9 [teamone/server-fix-good: ahead 3, behind 1] This should do it testing 5ea463a Try something new Така можем да видим, че нашият iss53 локален клон проследява origin/iss53 и че е напред с две, което значи, че локално имаме два къмита, които не са изпратени към сървъра. Можем също да видим, че master клона следи origin/master и е актуален. След това виждаме, че serverfix следи server-fix-good клона от отдалеченото хранилище teamone и е напред с три и назад с едно, което значи, че на сървъра има един къмит, който още не сме слели локално и три локални къмита, които не са пратени на сървъра. Накрая, виждаме че локалния ни клон testing не следи нито един отдалечен клон. Важно е да запомним, че тези цифри са актуални към момента на последното изпълнение на git fetch за всеки сървър. Командата не се свързва със сървърите, а само ни казва какво е кеширала локално от последната комуникация с всеки от тях. Ако желаете актуални ahead/behind статистики, преди нея трябва да обновите кеша с отдалечения статус: $ git fetch --all; git branch -vv ==== Pulling (изтегляне и сливане) Вече казахме, че командата git fetch изтегля от сървъра всички промени, които все още нямате локално, но не променя нищо в работната директория. Тя просто ще изтегли данните и ще ви позволи да ги слеете сами. Обаче, съществува команда git pull , която по същество е git fetch последвана от автоматично изпълнение на git merge в повечето случаи. Ако имате проследяващ клон създаден по начина по-горе, изрично посочен от вас или автоматично създаден като следствие от командите clone или checkout , то git pull последователно ще потърси кое отдалечено хранилище и клон са следени от текущия локален клон, след това ще изтегли информацията от тях и ще се опита да я слее автоматично в локалния клон. В общия случай е по-добре да използвате fetch и merge , защото понякога магията на git pull може да създаде недоразумения. ==== Изтриване на отдалечени клонове Да допуснем, че сте готови с отдалечения клон - да кажем че колегите ви са свършили работа по определена функционалност и са я слели в отдалечения ви master клон (или както и да се казва клона, в който е стабилния код). Можете да изтриете отдалечения клон с параметъра --delete на git push . Ако искате да изтриете serverfix клона от сървъра, изпълнете: $ git push origin --delete serverfix To https://github.com/schacon/simplegit - [deleted] serverfix Всичко, което това прави е да изтрие указателя от сървъра. Git сървърът в повечето случаи ще пази данните за известно време докато мине garbage collection системата му, така че случайно изтритите данни често могат лесно да се възстановят. === Пребазиране на клонове В Git съществуват два основни начина за интегриране на промени от един клон код в друг: сливане ( merge ) и пребазиране ( rebase ). В тази секция ще научите какво е пребазирането, как да го правите, защо е мощен инструмент и кои са случаите, в които не бихте искали да го използвате. ==== Просто пребазиране Ако се върнете назад до по-ранния пример в Сливане , можете да си припомните, че работата ви се разклонява и вие правихте къмити в два различни клона. Фигура 35. Проста история на разклоняването Най-лесният начин за интегрирането на клоновете, както вече разгледахме, беше командата merge . Тя изпълнява трипосочно сливане между най-новите snapshot-и от клоновете ( C3 и C4 ) и най-близкия им общ предшественик ( C2 ) създавайки нов snapshot (и къмит). Фигура 36. Сливане за интегриране на разклонена работна история Обаче, съществува и друг начин да направите това: можете да вземете patch на промените, които са въведени с C4 и да ги приложите върху C3 . В Git това се нарича пребазиране, rebasing . С командата rebase , вие вземате всички промени къмитнати в един клон и ги пускате в друг такъв. В този пример, ще извлечете клона experiment и ще го пребазирате върху master по следния начин: $ git checkout experiment $ git rebase master First, rewinding head to replay your work on top of it... Applying: added staged command Това става, като се намери най-близкия общ предшестващ къмит на двата клона (този върху, който сте в момента и този, който ще пребазирате), вземат се разликите въведени от всеки къмит на клона, върху който сте, разликите се записват във временни файлове, текущият клон се ресетва към същия къмит, в който е клона, който ще се пребазира, и накрая се прилага всяка промяна поред. Фигура 37. Пребазиране на промяната от C4 в C3 В този момент, можете да се върнете към master клона и да направите fast-forward сливане. $ git checkout master $ git merge experiment Фигура 38. Fast-forwarding на клона master Сега snapshot-ът, към който сочи C4' е точно същият като този, към който сочеше C5 в the merge example . Няма разлика в крайния резултат от интеграцията, но пребазирането прави историята по-чиста. Ако изследвате лога на един пребазиран клон код, той ще прилича на линейна история, цялата работа изглежда като случила се на серии, дори когато в действителност е била паралелна. Често ще правите това за да се уверите, че вашите къмити се прилагат безпроблемно върху отдалечен клон — вероятно проект, към който се опитвате да допринесете, но който не поддържате като автор. В този случай, вие вършите своята дейност в собствен клон и след това пребазирате работата си върху origin/master , когато сте готови да изпратите своите поправки в основния проект. По този начин, поддръжащият проекта разработчик не трябва да върши никаква работа по интеграцията на промените ви — просто ще направи fast-forward. Отбележете отново, че snapshot-ът, към който сочи финалния получил се къмит (бил той последния от пребазираните къмити за rebase или пък новосъздадения в резултат от merge) е един и същи и в двата случая — разликата е само в историята. Пребазирането прилага промените от една линия на разработка в друга по реда, в който те са били направени, докато сливането взема двата края на два клона и ги слива в едно. ==== Други интересни пребазирания Едно пребазиране може да бъде приложено и върху друг освен върху целевия му клон. Например, вижте фигурата История с topic клон произлизащ от друг topic клон . Създали сте един topic клон ( server ) за да добавите някаква сървърна функционалност към проекта си и сте направили къмит. След това, ползвайки този клон за отправна точка, сте създали нов такъв ( client ) за да направите някакви промени по клиентската част и сте къмитнали няколко пъти. Накрая, върнали сте се обратно към сървърния клон и сте направили още няколко къмита. Фигура 39. История с topic клон произлизащ от друг topic клон Да кажем, че решавате да слеете клиентските промени в master клона за публикуване, но желаете да си запазите server-side промените за допълнително тестване. Можете да вземете промените в клиентската част, които не присъстват на сървъра ( C8 and C9 ) и да ги приложите върху master клона чрез параметъра --onto на командата git rebase : $ git rebase --onto master server client Това звучи така, “Вземи клона client , разбери кои са промените в него след момента, в който този клон се е разклонил от server клона и ги приложи отново в него сякаш той е бил базиран първоначално на master клона.” Изглежда доста объркано, но резултатът е впечатляващ. Фигура 40. Пребазиране на topic клон от друг topic branch Сега можете да направите fast-forward на master клона (виж Fast-forwarding на master клона за включване на промените от клона client ): $ git checkout master $ git merge client Фигура 41. Fast-forwarding на master клона за включване на промените от клона client Нека кажем, че решите да интегрирате и промените от server клона. Можете да пребазирате server клона върху master без да се налага да превключвате към него изпълнявайки git rebase <basebranch> <topicbranch> — което вместо вас ще превключи към topicbranch (в този случай server ) и ще го приложи върху base branch (в случая master ): $ git rebase master server Това прилага вашите server промени върху master клона както е показано в Пребазиране на server клона в master клона . Фигура 42. Пребазиране на server клона в master клона След което, можете да превъртите основния клон ( master ): $ git checkout master $ git merge server Сега можете да изтриете клоновете client и server , защото те са интегрирани и не ви трябват повече, което ще направи историята на целия процес да изглежда така Историята на финалния къмит : $ git branch -d client $ git branch -d server Фигура 43. Историята на финалния къмит ==== Опасности при пребазиране Както можете да се досетите, пребазирането си има и недостатъци, които могат да се обобщят в едно изречение: Не пребазирайте къмити, които съществуват извън вашето собствено хранилище и върху които други хора може да са базирали работата си. Послушате ли този съвет, ще сте ОК. Не го ли направите, ще ви намразят. Когато пребазирате неща, вие зарязвате съществуващи къмити и създавате нови, които са подобни, но не съвсем същите. Ако изпратите къмитите някъде и други ваши колеги ги издърпат и използват като изходна точка за тяхната работа, а след това вие ги презапишете с git rebase и ги изпратите отново, то колегите ви ще трябва да слеят отново тяхната работа и нещата бързо ще придобият грозен вид, когато пък вие се опитате да изтеглите тяхната работа обратно за ваше ползване. Нека видим един пример, как пребазирането на публична работа може да доведе до проблеми. Да допуснем, че клонирате от централен сървър и вършите някаква работа след това. Историята на къмитите ви изглежда по подобен начин: Фигура 44. Клонирайте хранилище и направете промени по него Сега, някой друг върши друга работа, която включва сливане и я изпраща към централния сървър. Вие я издърпвате и сливате новия отдалечен клон във вашата работа, така че историята придобива подобен вид: Фигура 45. Издърпвате още къмити и ги сливате във вашата работа След това човекът, който е изпратил слетите си промени, решава да се върне назад и да пребазира работата си изпълнявайки git push --force за да презапише историята на сървъра. Вие от своя страна, издърпвате отново от сървъра получавайки новите къмити. Фигура 46. Някой изпраща към сървъра пребазирани къмити, изоставяйки тези, върху които вие сте базирали работата си Сега и двамата сте в бъркотия. Ако направите git pull , ще се създаде merge commit, който включва и двете линни история и хранилището ви ще изглежда така: Фигура 47. Вие сливате в същата работа отново, в нов merge commit Ако пуснете git log в история като тази, ще видите два къмита с един и същи автор, дата и съобщение, което ще е доста смущаващо. По-нататък, ако изпратите тази история обратно към сървъра, ще запишете допълнително в него всички тези пребазирани къмити, което би объркало допълнително хората в бъдеще. Безопасно е да предположите, че другият ви колега не желае C4 и C6 да присъстват в историята - в края на краищата това е причината той да направи пребазирането. ==== Пребазиране по време на пребазиране Ако се окажете в подобна ситуация, Git разполага с допълнителни средства, които да ви помогнат. Ако някой от вашия екип форсирано изпрати промени, които презаписват нещата, които служат за база на вашата работа, трудността за вас ще е да откриете кое е ваше и какво е било презаписано. Оказва се, че в допълнение към SHA-1 чексумата на къмита, Git също така калкулира и чексума, която е базирана на поправката (patch-ът) въведена от него. Това се нарича “patch-id”. Ако издърпате работа, която е била пренаписана и я пребазирате върху новите къмити на вашия колега, Git често може успешно да определи кое е изцяло ваше и да ги приложи обратно върху новия клон. Например, в предишния сценарий, ако вместо да правим сливане докато сме в момента показан на фигурата Някой изпраща към сървъра пребазирани къмити, изоставяйки тези, върху които вие сте базирали работата си , изпълним git rebase teamone/master , Git ще направи следното: Ще определи коя работа е уникална за нашия клон (C2, C3, C4, C6, C7) Ще определи кои от къмитите не са (C2, C3, C4) Ще определи кои къмити не са били презаписани в целевия клон (само C2 и C3, защото C4 е същият patch като C4') Ще приложи тези къмити върху teamone/master Така вместо резултатите, които виждаме във Вие сливате в същата работа отново, в нов merge commit , ще получим нещо приличащо повече на Пребазиране върху форсирано изпратена пребазирана работа Фигура 48. Пребазиране върху форсирано изпратена пребазирана работа Това работи само, ако C4 и C4 , направени от колегата ви са почти един и същи patch. В противен случай, пребазирането няма да може да установи, че това е дублиране и ще добави още един подобен на C4 patch (който вероятно няма да може да се приложи чисто, понеже промените вече ще са поне някъде там). Можете също така да опростите това изпълнявайки git pull --rebase , вместо нормален git pull . Или можете да го направите ръчно с git fetch последвана от git rebase teamone/master в този случай. Ако използвате git pull и искате да включите --rebase аргумента по подразбиране, можете да зададете pull.rebase конфигурационната стойност с git config --global pull.rebase true . Ако пребазирате само къмити, които никога не са били публични, а са съществували само в локалния компютър - тогава няма да имате проблеми. Ако пребазирате публикувани вече къмити, за които знаете че никога не са използвани от някой друг - тогава също няма проблем. Ако обаче пребазирате къмити, които вече са изпратени и може би използвани като основа за работата на някой друг в екипа, тогава очаквайте много проблеми и негативно отношение в съвместната ви работа с колегите. Ако вие или ваш колега установи към даден момент, че това е необходимо - уверете се, че поне всеки знае и пуска git pull --rebase за да се намалят неудобствата, когато проблемите дойдат. ==== Пребазиране или сливане Сега, когато видяхте в действие пребазирането и сливането, може би се питате кое от двете е по-добро. Преди да отговорим, нека се върнем малко назад и да поговорим за това какво означава историята. Една възможна дефиниция е, че историята на къмитите във вашето хранилище е запис на това какво в действителност се е случвало. Това е исторически документ, ценен сам по себе си, който не бива да се модифицира. Погледнато по този начин, излиза че промяната на историята на къмитите е почти богохулство - вие лъжете за това какво се е случвало всъщност. А какво ще е ако имахте разхвърляни серии от merge къмити? Ами - просто така са протекли нещата и хранилището следва да пази този факт за идните поколения. Обратната гледна точка приема историята като хронология на това как проектът ви е бил създаден . Например, не бихте публикували първата чернова на една книга и ръководството за това как да поддържате вашия софтуер заслужава внимателно редактиране. Когато работите върху проект, може да ви трябва запис на всичките ви погрешни стъпки, но когато дойде време да споделите проекта с останалите, вероятно ще искате да покажете съвсем ясно как сте стигнали от точка А до точка В. Това е гледната точка на поддръжниците на инструменти като rebase и filter-branch , които искат да разкажат историята на проекта не буквално каквато е била, а каквато би била най-полезна за тези, които ще го поемат в бъдеще. Обратно на въпроса кое е по-добро, пребазирането или сливането? Надяваме се виждате и сами, че отговорът не може да е еднозначен. Git е мощна система, която ви позволява да правите много неща с историята на проекта, но няма еднакви екипи и няма еднакви проекти. Накратко, най-добрият отговор на въпроса е, че трябва сами да решите кой подход е най-добър според конретната специфична ситуация. Ако се колебаете, но искате да се възползвате от предимствата и на двата подхода, просто помнете това правило - спокойно използвайте пребазиране за локални промени, които сте направили, но не са публични. Така ще си подредите историята в чист вид. Но никога не пребазирайте нещо, което вече сте изпратили за споделено ползване. === Обобщение Разгледахме основите на разклоненията и сливанията в Git. Би следвало сега да умеете с лекота да създавате и превключвате клонове, както и да сливате локални клонове заедно. Също така, би следвало да можете да споделяте клоновете си код изпращайки ги към общ сървър, да работите с други колеги по споделени клонове код и да пребазирате вашите клонове преди споделянето им. Следва да разгледаме какви ви е необходимо за да си пуснете свой собствен хостинг сървър за Git хранилища. == Git на сървъра На този етап, би следвало да можете да вършите повечето си ежедневна работа, за която ви е нужен Git. Обаче, за да участвате с вашия труд в какъвто и да било вид съв | 2026-01-13T09:29:41 |
https://lwn.net/Articles/897202/ | ioctl() forever? [LWN.net] LWN .net News from the source Content Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us Edition Return to the Front page User: Password: | | Log in / Subscribe / Register ioctl() forever? Ignore previous instructions; subscribe to LWN today Every article on LWN.net is written by humans, for humans. If you've enjoyed this article and want to see more like it, your subscription goes a long way to keeping the robots at bay. We are offering a free one-month trial subscription (no credit card required) to get you started. By Jake Edge June 8, 2022 LSFMM In a combined storage and filesystem session at the 2022 Linux Storage, Filesystem, Memory-management and BPF Summit (LSFMM), Luis Chamberlain and James Bottomley led a discussion about the use of ioctl() as a mechanism for configuration. There are plenty of downsides to the use of ioctl() commands, and alternatives exist, but in general kernel developers have chosen to continue using this multiplexing system call. While there is interest in changing things, at least in some quarters, the discussion did not seem to indicate major changes on the horizon. Problems Chamberlain began with a history lesson with "some rants" thrown in. ioctl() is still used a lot by filesystems and the block layer in Linux, but the wireless-networking subsystem, which he used to work on, successfully shifted away from ioctl() . The system call "wasn't really originally designed for what we think it was", he said; it is "essentially a hack". In Douglas McIlroy's history of Unix , it was called "a closet full of skeletons" that was mainly used to prevent the addition of too many new system calls. Those things should be kept in mind when thinking about ioctl() , he said. The first version of Linux did not have ioctl() ; it was added in Linux-0.96a in May 1992. A small patch in 1993 changed a type from unsigned int to unsigned long , which eventually led to compatibility headaches for 32-bit ioctl() calls issued on 64-bit systems. The Unix idea that everything is a file is useful because it allows for flexibility, but it also allows for lazy API design, he said. Beyond that, ioctl() commands are not well documented and the interface does not allow for introspection Lack of introspection abilities is not a problem that Chamberlain has encountered directly, so he asked Bottomley to elaborate on that. The problem crops up in the container world, Bottomley said, and it is not just for ioctl() commands but also introspection for system calls. For example, securing a Docker container by limiting the system calls it can make does not really secure anything if there are opaque ioctl() commands that can be used to circumvent the restrictions. So there is a lot of concern about non-introspective interfaces because they "can't be policed properly by the tools we usually use for containers, like seccomp and even eBPF". The specific problem with ioctl() is that there is a "dense binary packet" that gets passed into the call, which makes it difficult for external tools to deduce what the packet contains. In theory, the kernel could switch to using XML or JSON, but that does not really change the underlying problem much, he said. The introspection problem remains "almost regardless of which interface we choose". There are other problems with ioctl() , Chamberlain said. For example, he asked Arnd Bergmann about ioctl() support for different architectures. He got back an itemized list of caveats. "The world is not peachy for architecture support as well". Greener grass The Linux wireless-networking configuration underwent a shift from the ioctl() -based wireless extensions to the netlink-based nl80211 interface. Chamberlain invited attendees to compare include/uapi/linux/wireless.h with include/uapi/linux/nl80211.h to see how much cleaner the new interface is. The netlink interface is not designed to be generic, so it may not be the right choice for filesystems and the block layer. But he is sure that that it is possible to find something better than the ioctl() -based interface we have now. Chamberlain handed the microphone back to Bottomley so that he could talk about configfd as a possibility. But Bottomley said that he was not going to promote configfd, though he did describe it a bit. It came out of his efforts on the shiftfs filesystem , which was eventually supplanted by ID-mapped mounts . Configfd was based on the fsconfig() system call, which allows setting a bunch of configuration information on a filesystem atomically, but configfd was bidirectional. David Howells, who developed fsconfig() and the related new mounting API , interjected that fsconfig() was originally bidirectional as well, though Al Viro removed that piece before it was merged. Instead of defending configfd, Bottomley said, he wanted to talk about the necessity of ioctl() . When there is a need for "an exception to the normal semantic order of things", an ioctl() command can provide it. And there will always be a need for exceptions, no matter how tightly regulated that semantic order is. There will always be a requirement that two parties be able to communicate data that cannot be structured using the existing mechanisms—an exception. Whether that data is sent as JSON, XML, or binary data, it is, effectively, an ioctl() . The introspection problem is real, but is one that he thinks could be handled with documentation. Christian Brauner said that the problem goes beyond just ioctl() ; there are a number of different problems with seccomp() filtering because of the need to inspect the system call arguments to help make filtering decisions. Pointer arguments have been discouraged for new system calls because seccomp() cannot follow the pointers. But using pointers to structures is a technique for creating extensible system calls , so seccomp() also needs to change. It is a problem "slightly to the side" of the ioctl() problem, but it needs to be solved as well, he said. Bottomley said that this shows that even if it were decreed that ioctl() commands should all move to new system calls, the problem with introspection would just move with it. Ted Ts'o said that kernel developers rightly keep a tight grip on new system calls and their interfaces. So adding a new system call involves an enormous bikeshedding exercise with lots of additional requirements, including documentation and working with features like seccomp() filtering. Often, the feature developer does not care about the container use case, even if they should, so they move it to an ioctl() command "so they can dodge the bikeshedding". The more perfect the kernel community tries to make the system call interface, the more incentive there is for developers to route around it, Ts'o said. He has heard people talk about adding a feature via a filesystem-specific ioctl() command as a way to avoid the "fsdevel bikeshed party". That is unfortunate, since there is plenty of useful architectural review that might come with trying to make the feature more widely usable, but it is understandable that people take the expedient approach. No one has infinite resources, Ts'o said. Alternatives Josef Bacik asked what the alternative is. "You're going to pry ioctl() s from my cold dead hands unless you give me something else." The Btrfs developers have "wasted a lot of time" in grand architectural discussions that ended up with the community saying that a feature should just be put into an ioctl() command—after a year of discussion. Bottomley said that he would argue ioctl() commands, used judiciously, are just fine. Kent Overstreet said that ioctl() commands are simply a driver-specific system call; there is a real need for that. It provides a mechanism to try out a feature in a more private way before it gets promoted to a system call, where it becomes permanent. Amir Goldstein agreed, noting that the "chattr" ioctl() command was implemented by two different filesystems before it was determined to be a generally useful feature and moved into the virtual filesystem (VFS) layer. There are multiple existing mechanisms for configuration in the kernel, Ts'o said. ioctl() commands are just system calls in disguise, both of which provide ways to do configuration, but procfs and sysfs files can also be used for that. Beyond those, the new mount API or configfd provide other configuration mechanisms. But which gets used depends in part on how much pain there is in trying to change the mechanism for a new task, he said. If the pain of adding ioctl() commands rises to the same level as for system calls, developers will simply find a "different escape hatch". But Chamberlain said that adding new wireless commands did not require additional system calls or ioctl() commands because it uses netlink. Those changes can be made in a domain-specific place without all of the problems that come from the other mechanisms. Brauner said that he had a hard time seeing what could replace the ioctl() interface, however; he wondered if Chamberlain was suggesting switching to something netlink-based. Chamberlain said that it was just one idea, but Howells noted that netlink could not be used because it depends on networking being configured into the kernel, which is not always the case. There was some discussion of alternatives, but it is clear that ioctl() itself is not going away and that it fills a need. Finding ways to make the ioctl() arguments more introspectable would be useful, as would better documentation. But if requiring those things causes the friction level for adding new commands to rise too much, it will have the opposite of its intended effect. No real solution seemed to be forthcoming from the discussion, though no one seems entirely satisfied with the status quo either. Index entries for this article Kernel ioctl() Conference Storage, Filesystem, Memory-Management and BPF Summit/2022 to post comments ioctl() forever? Posted Jun 8, 2022 14:48 UTC (Wed) by rincebrain (subscriber, #69638) [ Link ] (1 responses) People might also use ioctl because they're developers on something out of tree, the existing syscalls and ioctls have artificial limitations, and LKML has been actively hostile to anyone suggesting anything happen or not to improve things for projects which are unlikely to ever be mainlinable. So, since you can't easily add custom syscalls to everyone ever, ioctl it is. ioctl() forever? Posted Jun 18, 2022 21:33 UTC (Sat) by developer122 (guest, #152928) [ Link ] There is a stunning level of hostility, regardless of licence. ioctl() forever? Posted Jun 8, 2022 15:18 UTC (Wed) by josh (subscriber, #17465) [ Link ] One other issue with ioctl: it can mean different things to different devices, and there's no guarantee of non-overlap (even though the kernel does attempt to avoid it). So if a filter mechanism needs to allow a particular ioctl, used with a particular device, it might also be allowing other unrelated and problematic ioctls on other devices that use the same ioctl number. ioctl() forever? Posted Jun 8, 2022 15:52 UTC (Wed) by tau (subscriber, #79651) [ Link ] (9 responses) There is also a tendency to crowbar a kernel's API semantics into the language of a virtual filesystem, with virtual directories containing virtual text files. A compromise between machine readable and human friendly while being a poor fit for both. For relatively high-overhead and semantically complicated "system calls" I think that it would be nice if there was some sort of unified standard for user space and kernel space message passing that had a strong emphasis on message schemas and extensibility. Something like dbus. Or gRPC without all of the horrible HTTP/2 trappings. Or something with a design more suited to asynchronous communication like Wayland. Good luck getting a useful number of people to agree on what such a protocol should look like though. Of course it is very easy to say "it would be nice if" on a message board. ioctl() forever? Posted Jun 8, 2022 18:34 UTC (Wed) by jhoblitt (subscriber, #77733) [ Link ] (5 responses) A solution similar to gRPC doesn't sound unreasonable. Protobufs, as an API specification, are much easier to machine process than the entirety of the C language. Protobufs also support schema evolution. ioctl() forever? Posted Jun 8, 2022 20:07 UTC (Wed) by wahern (subscriber, #37304) [ Link ] (4 responses) > Protobufs, as an API specification, are much easier to machine process than the entirety of the C language. With CTF/BTF symbols, sticking to C would be easier and simpler for all involved, especially when you begin to look at what would be the most difficult part of structured, compound, nested data type filtering--actual filter specifications and execution. The obvious solution is a BPF program, which is precisely why BTF symbols were added to the kernel--so BPF programs could introspect kernel data types. ioctl() forever? Posted Jun 8, 2022 20:25 UTC (Wed) by Cyberax ( ✭ supporter ✭ , #52523) [ Link ] (3 responses) Even with CTF you still have problems with strings. ioctl() forever? Posted Jun 9, 2022 13:37 UTC (Thu) by nix (subscriber, #2304) [ Link ] (2 responses) Yeah, but that's neither CTF nor BTF's fault: that's the same problem with dereferencing pointers (and finding a way to do that while not allowing attackers to modify the thing and sneak bad stuff past you via TOCTTOU races, *without* incurring horrible overhead by forcing every such pointed-to thing to be CoWed on modification). ioctl() forever? Posted Jun 9, 2022 18:44 UTC (Thu) by Cyberax ( ✭ supporter ✭ , #52523) [ Link ] (1 responses) That's why just marshalling all the data into variable-length structures that can be simply copied into the kernel space is the right way to do it. Yes, you have some overhead duet to packing and copying, but both are pretty efficient. Also, ioctl()s shouldn't be performance-critical anyway. ioctl() forever? Posted Jun 9, 2022 23:14 UTC (Thu) by wahern (subscriber, #37304) [ Link ] With CTF symbols you could easily write a simple function to recursively copy a data structure into kernel space. So you end up in the same place, but with a fraction of the complexity and code. For C string members you can trivially implement constraint checking during the copy. Similarly, for dependent pointer and size members you can include simple qualifiers in the structure definition that the copy routine can validate. (There was a proposal, effectively implementing a simple dependent type system for this case, which came close to passing muster for the next C2x revision. It seems to have failed for lack of real-world implementation experience, but strictly speaking it should be quite simple to implement.) Alternatively, you could implement a type-safe unpacking API. (If you only care about memory safety, you might not even need CTF.) For example, "give me the next member, which I expect to be a NUL-terminated string". This may be more or less ergonomic than the above, but either way would provide the same effective interface as generic deserializers--even "zero copy" serialization formats typically cannot be exposed as plain C data structures, even when the serialization and deserialization code is generated a la Cap'n Proto. The difference between `string_t getNamedField(object_t)` and `string_t copy_in_string(userstruct_t *, cursor_t *)` is purely syntactical when you can't completely trust the input to be well formed, which we can't. In any event, simple intermediations, with or without CTF, provide avenues to enjoying all the same safety guarantees, without creating both kernel and userland dependencies on enormous (10-100+k SLoC) libraries. Microkernels tend to heavily rely on serialized message passing and/or RPC code generators. I'm sure they work well, but there's a steep upfront cost, especially when it comes to tooling. Maybe even a simpler alternative is it avoid variable length strings entirely. Briefly looking at existing ioctls, it seemed like most string fields within structures are fixed-sized arrays. Variable length strings seemed more likely to be passed directly as an argument. (But please feel free to set me straight on that account as I didn't look very hard and certainly didn't write any tools to analyze the types.) To the extent the latter are a problem, they could be fixed with a very thin intermediating interface. There's something to be said for simply using fixed-sized arrays. During the heyday of writing GNU replacements for proprietary tools, there was an emphasis on removing arbitrary limitations and permitting every conceivable type of input to be variable length and unbounded; that emphasis became pervasive and reflected in even trivial, internal interfaces removed from user input. That's rarely needed, and rarely warranted given the resulting complexity, *especially* for kernel interfaces. Even file paths (or more specifically, file path arguments) have a fixed upper bound in the Linux kernel. Recently I discovered this was true even in Solaris, despite Solaris have a complicated kernel syscall facility for unbounded-length input and output syscall arguments. If you step away from trying to making everything configurable and unbounded, then it becomes much easier to limit complexity. Usually you can set an upper bound that is good enough and move on; and for many of the exceptions, you can switch to semantics that let you trade time for space (i.e. trade serial processing for discrete buffers). Or to put it another way, for the rare cases where setting fixed-bound arguments is too cumbersome, use netlink instead of ioctl. Problem solved. One doesn't need to become the other, or replaced with something fancier; just make the choice more clear. If you want to make it easier to prevent people from accidentally doing the wrong thing, and to identify places where that might be likely, you can add type annotations to structures and other types used by kernel ioctl interfaces, complemented with a GCC module pass that identifies code that directly access members. IOW, you can implement something akin to Rust's type checker that prevents normal code from reading pointers in an unstructured manner, forcing that code to go through a "safe" API. ioctl() forever? Posted Jun 8, 2022 18:41 UTC (Wed) by atnot (guest, #124910) [ Link ] (2 responses) > There is also a tendency to crowbar a kernel's API semantics into the language of a virtual filesystem, with virtual directories containing virtual text files I don't remember who said this, but the lesson should not have been "everything is a file" being good, but "everything is a file descriptor" being good. There is great value in having a unified way of representing kernel resources and associated access capabilities, one that can easily be shared between subsystems and passed between processes. But the part where you usually need to obtain those file descriptors by painfully funneling everything through hundreds of snprintf() and open() calls on hardcoded paths isn't actually that valuable. In fact it often only undermines those valuable properties. ioctl() forever? Posted Jun 9, 2022 0:53 UTC (Thu) by NYKevin (subscriber, #129325) [ Link ] (1 responses) Meh, snprintf isn't the kernel's fault, it's C's fault for being terrible at finagling strings. Stringly-typed interfaces are bad because they are difficult or impossible to validate, not because snprintf is painful. ioctl() forever? Posted Jun 9, 2022 1:35 UTC (Thu) by atnot (guest, #124910) [ Link ] This wasn't at all meant to be a dig at snprintf(), feel free to insert your preferred mechanism. I just don't think string formatting is something that should be regularly involved at the very core of OS APIs at all, even if C's string handling wasn't as uniquely terrible as it is. Although that fact doesn't help of course. ioctl() forever? Posted Jun 8, 2022 18:38 UTC (Wed) by jhoblitt (subscriber, #77733) [ Link ] (1 responses) What is the functional difference between an ioctl() and an undocumented / unreviewed system call? ioctl() forever? Posted Jun 9, 2022 13:33 UTC (Thu) by khim (subscriber, #9252) [ Link ] Ability to avoid clashes. Even if out-of-tree device uses the same number as another out-of-tree device they don't affect each other because, well, they are different devices. Syscall numbers are globals, on the other hand. ioctl() forever? Posted Jun 8, 2022 19:12 UTC (Wed) by koverstreet ( ✭ supporter ✭ , #4296) [ Link ] (20 responses) Here's my ioctl v2 proposal that came out of that discussion - something lightweight and minimal that would make ioctls more like normal function/syscalls: https://lore.kernel.org/lkml/20220520161652.rmhqlvwvfrvsk... ioctl() forever? Posted Jun 8, 2022 20:32 UTC (Wed) by roc (subscriber, #30627) [ Link ] (19 responses) For rr we really want to be able to determine, from the parameters and results of a syscall, all the userspace memory locations that a syscall writes to. Other tools (e.g. fuzzers) need the memory locations read as well. This is particularly hard for ioctls. The current ioctl op format is supposed to tell us the size of the data pointed to by the pointer, and whether it's read or written or both, but this information is often incomplete or plain wrong. In the worst cases, the data in that struct is just the root of some elaborate data structure with many other userspace pointers in it. So it would be great if an ioctlv2 design solves this. One way would be to provide metadata allowing us to parse the layout *and making the correctness of that metadata testable by automated tests*. Another way would just be to require that the data be a single contiguous buffer. ioctl() forever? Posted Jun 8, 2022 21:24 UTC (Wed) by koverstreet ( ✭ supporter ✭ , #4296) [ Link ] (18 responses) hey, I was just trying rr for my first time today! I'm not sure how practical it'll be to solve this problem in general. My approach was to try and make ioctls more like syscalls - i.e. something that looks like a normal function call. That would make the simple cases simpler, by getting rid of ioctl structs entirely for the simple cases. But this won't do anything for the more complex cases you brought up. The problem in those cases is just that C is a very low level language, and anything that's complex enough to handle those cases isn't going to feel natural and simple in C. This is my complaint with those advocating netlink as a wholesale replacement for ioctls - it's more complicated than it needs to be for the simple cases. But for the more complicated cases maybe it's the right approach. There's another possibility that just occurred to me because I saw you were using it today - cap'n proto. If the problem is that defining complex data structures in a portable, ABI independent way sucks, this is exactly what cap'n proto is intended for. When I last looked at it the story for using it from C seemed incomplete, but maybe this has changed - might be worth another look. For those unfamiliar: cap'n proto [1] is a schema language for defining ABI independent types. Crucially, unlike things like protobufs, it doesn't have pack/unpack operations - the wire format is the in memory format. It's like defining types in C using only standard sized integers, only without all the razor sharp edges and some really useful features. 1: https://capnproto.org/ ioctl() forever? Posted Jun 8, 2022 21:32 UTC (Wed) by abatters ( ✭ supporter ✭ , #6932) [ Link ] In case it's useful, here is a concrete example of a complex ioctl: https://sg.danny.cz/sg/sg_v40.html The sg driver has ioctls for sending generic SCSI commands, so it supports read-type, write-type, and bidirectional commands, direct I/O, pointers to arrays of iovecs of userspace buffers like readv/writev, pointers to buffers to contain error information, async I/O, and lots of other complex features, and it has to be high-performance. It's sort of like io_submit() and io_getevents() for SCSI commands in an ioctl(). ioctl() forever? Posted Jun 9, 2022 5:43 UTC (Thu) by wahern (subscriber, #37304) [ Link ] (1 responses) Unix has had a standardized serialization format for decades: XDR. https://en.wikipedia.org/wiki/External_Data_Representation An encoder/decoder has been in the Linux source tree since almost the beginning: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/... If better serialization formats sufficiently resolved these issues then presumably ioctl would already be gone, replaced by something using XDR or one of the other dozen similar formats that have come and gone over the years. The marginal benefit of these formats over plain C data structures is manifestly not that great, at least for local IPC. ioctl() forever? Posted Jun 9, 2022 6:39 UTC (Thu) by roc (subscriber, #30627) [ Link ] Many ioctls were invented before rr or fuzzers or security mattered, and then all the other ioctls were added because that's just how things are done. ioctl() forever? Posted Jun 9, 2022 6:55 UTC (Thu) by pm215 (subscriber, #98099) [ Link ] (14 responses) I think a lot of the problem is that the kernel refuses to define its ABI in any other way than "here's a pile of header files, and if you're lucky also some documentation". This is a pain for any case except "I'm a C program". ioctl isn't the only offender here either -- setsockopt is another "feed arbitrary data structures via a generic-looking interface" mechanism. QEMU's user-mode emulation runs into trouble with these things because we have to convert from guest architecture struct layout and endianness to host layout and endianness; without a machine-readable definition of what's being passed around by ioctl and similar syscalls we have to hand-roll support for every new ioctl somebody cares about. And every so often we run into one that's just straight-up not even documented. ioctl() forever? Posted Jun 9, 2022 7:33 UTC (Thu) by roc (subscriber, #30627) [ Link ] (11 responses) We really should come up with a shared description of the syscall ABI that can be used by QEMU, rr, fuzzers, ASAN, Valgrind, etc. I think we're all duplicating work. ioctl() forever? Posted Jun 9, 2022 7:35 UTC (Thu) by roc (subscriber, #30627) [ Link ] Syzkaller has an abstract description of syscalls: https://github.com/google/syzkaller/blob/master/docs/sysc... It's fairly fuzzer-specific of course. ioctl() forever? Posted Jun 9, 2022 11:38 UTC (Thu) by adobriyan (subscriber, #30858) [ Link ] And ship it with kernel: mount -t abi ... ! ioctl() forever? Posted Jun 9, 2022 15:11 UTC (Thu) by ejr (subscriber, #51652) [ Link ] (8 responses) To paraphrase the bard, "That way [formal methods] lie; let me shun that." ioctl() forever? Posted Jun 12, 2022 0:16 UTC (Sun) by developer122 (guest, #152928) [ Link ] (7 responses) Such is the pervading wisdom in software. It was yesterday I was commented that modern security practice is to layer incomplete speedbumps one by one and call it "defense in depth." This was in response to new bypass of the M1's hardware pointer checking, a "last line of defense." None of these half-baked measures qualify as defense in depth. Anyone who calls it that is kidding themselves. They're deployed one by one with large time spans inbetween, reactively to whatever attackers currently favor. It should come as no surprise that attackers have no problem paying a low continual cost to work around each new measure, in return for continued ability to exploit hosts. Meanwhile, we plaster over the undefined behavior that makes C/C++ static analysis impractical. We don't even talk about how CPUs work. We continue to ignore that actual exploit *theory* exists, like the Weird Machine whose wikipedia page starts: "Exploits exist empirically, but were not studied from a theoretical perspective prior to the emergence of the framework of weird machines." This makes it impossible to analyze systems holistically, and to find and shut out entire classes of exploits. Civil engineering eventually got past "I think we can cut a small hole in this wall" and reached "lets calculate the loads and strains." Electrical engineering stopped electrocuting frogs and developed Maxwell's laws. Right now computing is still far behind all others and until formal methods and theory take over, we won't ever make statements like "this bridge will stand for 100 years." ioctl() forever? Posted Jun 12, 2022 1:15 UTC (Sun) by Cyberax ( ✭ supporter ✭ , #52523) [ Link ] (6 responses) > Electrical engineering stopped electrocuting frogs and developed Maxwell's laws. Open the NEC and look for any mentions of Maxwell's equations. If anything, modern safety engineering is built on installing as many "speedbumps" as possible, rather than on making everything perfectly safe. ioctl() forever? Posted Jun 12, 2022 9:01 UTC (Sun) by farnz (subscriber, #17727) [ Link ] (5 responses) The NEC (and its international equivalents) are guides to safe installation, not to electrical engineering. It says that if you purchase products that have been engineered to a suitable standard, and then install them following this guide, you will be safe enough. The components you install when you buy the things that the NEC requires are engineered with things like Maxwell's laws as guidance - a GFCI or an AFCI or an ELCB or an overcurrent breaker, or even a simple switch is not just empirically designed to work as specified, but rather designed around the known laws of physics and then tested against the specification. It's just that we need the NEC rules because the possible range of components is not as wide as we'd like - and thus we need to allow for known physical issues when we install. For example, we need overcurrent breakers because wires have resistance and thus heat up when carrying current; a significant chunk of the NEC is describing the different ways you can install wires that meet a given standard, then place a breaker on the source end so that the wire cannot heat up enough to start a fire. ioctl() forever? Posted Jun 12, 2022 15:01 UTC (Sun) by ejr (subscriber, #51652) [ Link ] (4 responses) The main problem is that the market for electrical engineers actually *designing* these things is relatively static or slowly growing. Meanwhile, companies are absolutely desperate to fill programming seats. And if it ain't Python or Matlab/Octave, many students don't know it until maybe their third year. Maybe. If type checking is not mentally established, the core of current formal methods that include interactive proofs is going nowhere. (For the audience: Making a program compile without type errors *is* working with an interactive proof system called the compiler. The correct program is a proof of its being well-typed given the language's rules / axioms.) I also suspect you underestimate how often "throw it at the wall and see if it sticks" applies even in engineering fields. Or more appropriately "this worked for something kinda similar, so it'll work here." I recently learned of a wonderful text that can illustrate the kind of knowledge needed on the practical hardware side: D. M. Russinoff, Formal Verification of Floating-Point Hardware Design, https://doi.org/10.1007/978-3-030-87181-9_3 . It *appears* to be available gratis; I don't think I was redirected through an institutional subscription. Software potentially could be simpler in some areas, but the OS/device level requires a similar level of skill in finding the right model. That's a polite way of saying the kind of infinite bike-shedding that was happening with btrfs. If some research group can hit it out of the park like the formalization of RISC-V, sure, but people with product-like deadlines don't have that time. (I've been on both sides.) ioctl() forever? Posted Jun 12, 2022 15:37 UTC (Sun) by mpr22 (subscriber, #60784) [ Link ] (2 responses) You were in fact directed there by an institutional subscription :( For me, that link goes to a website run by Springer Nature, where I am informed that, as a private individual in the United Kingdom of Great Britain and Northern Ireland, I would have to pay £19.95 for a PDF of the Logical Operations chapter (pp 35-44) of ISBN 978-3-030-87181-9, £95.50 for the whole of ISBN 978-3-030-87181-9 as an eBook, or £119.99 for the whole of ISBN 978-3-030-87181-9 as a physical hardcover book (all prices inclusive of applicable VAT). ioctl() forever? Posted Jun 13, 2022 21:57 UTC (Mon) by ejr (subscriber, #51652) [ Link ] AUGH. Drat. Sorry! I was hoping, and I didn't see how I was already logged in. There is no RTL in the book at all but rather proofs based around integers. That's kinda how I think of circuits, so I like it. ioctl() forever? Posted Jun 14, 2022 12:54 UTC (Tue) by paulj (subscriber, #341) [ Link ] It is archived by sci-hub.se, depending on what you think of that kind of thing. ioctl() forever? Posted Jun 12, 2022 16:06 UTC (Sun) by farnz (subscriber, #17727) [ Link ] And underlying that is that electrical safety is a mature and well-understood field. The physics involved in a GFCI or an overcurrent breaker have been well-understood since the 19th century, and the physics required for an AFCI were fully settled before World War I in 1914. There's nothing in any NEC-compliant installation that a good physicist from 1920 couldn't fully understand and explain - although they'd be amazed by the manufacturing techniques involved (and would be seriously shocked by the IC in an AFCI, even though they could explain the physical principles that underpin its operation). In contrast, logic design (both software and hardware) is a rapidly evolving field even today - Rust's type system is based atop affine logic from the 1970s, and there's mathematics I'm aware of that's probably relevant to programming language design that was only formulated rigorously in the last 20 years, and where there's active leading-edge research trying to determine if it's useful, and if so, how. I'd also agree on the "throw it at the wall and see if it sticks" thing - the only time, IME, that engineers actually seriously bother with the rigorous analysis that's possible for something like a GFCI is when you're cost-optimizing it. Otherwise, it's considered too much work, when you can take a design that's probably overkill but meets requirements and ship it. ioctl() forever? Posted Jun 9, 2022 17:33 UTC (Thu) by nix (subscriber, #2304) [ Link ] (1 responses) This sort of thing is why CTF was added to the toolchain :) abigail has support for it now, too... of course ioctls don't all specify which structures they manipulate, but for those that *do*... ioctl() forever? Posted Jun 11, 2022 7:50 UTC (Sat) by pm215 (subscriber, #98099) [ Link ] How does CTF help here? I read https://lwn.net/Articles/795384/ which seems to describe it as basically a more compact debug info format, which leaves me unsure how it would be useful for describing the kernel ABI in a more machine-readable way. I guess in theory you could build the whole kernel and then fish out the debug info, but that would take forever and only have the info for the specific binary that got built... ioctl() forever? Posted Jun 9, 2022 11:02 UTC (Thu) by jengelh (subscriber, #33263) [ Link ] >that netlink could not be used because it depends on networking being configured into the kernel Perhaps when someone ponders its use for a component, what they really had in mind was just the serialization format, without the AF_NETLINK socket. You could still hand in a netlink-formatted stream via ioctl. Netlink has its own share of issues. One is the asynchronous model and the programming that this entails; you need to do two at least two calls (send/recv). Another is the 16-bit size fields in its serialization format. If you can't fit your stuff into one message because of that limit, you have to go on a multi-roundtrip endeavour from userspace. The kernel part meanwhile may need to keep extra state to logically tie the individual netlink messages together. That's kinda terrible. Speaking of ioctl, setsockopt is just the same. ioctl() forever? Posted Jun 9, 2022 11:42 UTC (Thu) by jazzy (subscriber, #132608) [ Link ] (4 responses) Has someone considered copying Windows? BOOL DeviceIoControl( [in] HANDLE hDevice, [in] DWORD dwIoControlCode, [in, optional] LPVOID lpInBuffer, [in] DWORD nInBufferSize, [out, optional] LPVOID lpOutBuffer, [in] DWORD nOutBufferSize, Basically it allows for invoking an IOCTL and pass in and/or pass out a continous buffer. To me this seems extendable and avoids the need to embed pointers. It also clearly specifies what is readable and writable. ioctl() forever? Posted Jun 9, 2022 19:02 UTC (Thu) by camhusmj38 (subscriber, #99234) [ Link ] (3 responses) I imagine they would rather eat their own hats. ioctl() forever? Posted Jun 9, 2022 19:25 UTC (Thu) by mathstuf (subscriber, #69389) [ Link ] (2 responses) I like how the metadata is "optional" when it probably means "nullable". I doubt calling this without those arguments at all works out that well in practice. ioctl() forever? Posted Jun 9, 2022 19:27 UTC (Thu) by camhusmj38 (subscriber, #99234) [ Link ] I looked it up - the rules are documented. Which combination of nulls are allowed - if you go the overlapped (async) route you can leave the number of bytes out null and vice versa. ioctl() forever? Posted Jun 9, 2022 19:47 UTC (Thu) by Cyberax ( ✭ supporter ✭ , #52523) [ Link ] It works fine for IOCTLs that don't need input or output parameters. ioctl() forever? Posted Jun 9, 2022 15:00 UTC (Thu) by karim (subscriber, #114) [ Link ] (6 responses) Just on the discoverability front, it would be great if there was a way to query any ioctl() interface for the commands it accepts and the parameters expected. A sort of obligatory man_ioctl() call on any kernel party that wants to expose ioctl(). I could then do something like "$ ioman /dev/foobar" and get a list of list of parameters, etc. Maybe even gate access to register an ioctl() on having said man_ioctl() registered along with it. ioctl() forever? Posted Jun 9, 2022 15:43 UTC (Thu) by mathstuf (subscriber, #69389) [ Link ] (5 responses) So, uh, what format will this communicate the requirements in? Snippets of C headers? ;) ioctl() forever? Posted Jun 9, 2022 15:54 UTC (Thu) by karim (subscriber, #114) [ Link ] (4 responses) man pages may have good examples. If you do a "man 2 open", for instance, it lists all possible open flags with a description. Maybe something like that? ioctl() forever? Posted Jun 9, 2022 16:27 UTC (Thu) by mathstuf (subscriber, #69389) [ Link ] (3 responses) From `ioman(1)`, sure. But what will `man_ioctl(2)` use to communicate whatever gets converted into groff format (or is the kernel going to speak groff directly?). ioctl() forever? Posted Jun 9, 2022 16:39 UTC (Thu) by karim (subscriber, #114) [ Link ] (2 responses) Very good question. I can't say I thought it all the way through. Maybe another inspiration could be online help output from commands that print options when you provide "-h" ... i.e. just some free-form text to be printed on screen when invoked. It's a rough cut of an idea. Definitely requires some more forethought to be useful. But, personally, I'd love to have a way to ask about the ioctl()s available for any /dev/foo and even have a tool to invoke them from the command line if it makes sense. ioctl() forever? Posted Jun 9, 2022 17:04 UTC (Thu) by NYKevin (subscriber, #129325) [ Link ] (1 responses) You can't force people to write documentation. If you try, you just end up with something like the following: > int FrobnicateSprocket(Sprocket *s) > Frobnicates a sprocket. > > Arguments: > s: The sprocket to frobnicate. > > Returns: > Zero if no error, or nonzero and sets errno. > > Errno values: > EPERM - Frobnicating this sprocket is not permitted. IMHO if you're going to do something like this, it should be a machine-readable enumeration of commands, not a man page. ioctl() forever? Posted Jun 11, 2022 12:26 UTC (Sat) by pm215 (subscriber, #98099) [ Link ] If you're the kernel maintainers you absolutely can force people to write documentation -- just refuse to merge any patch that adds a new syscall or ioctl and doesn't include documentation as part of the patchset. You can set the quality bar at any level you like. If stuff slips through the code review stage without sufficient documentation, you can revert it. In other words, allowing or not allowing undocumented new interfaces is a choice, just as allowing or not allowing changes that break userspace is a choice. Copyright © 2022, Eklektix, Inc. This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds | 2026-01-13T09:29:41 |
https://www.linkedin.com/uas/login?fromSignIn=true&session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fcoachhub&trk=top-card_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=COMPANY&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:41 |
https://www.digitalcameraworld.com/buying-guides/best-polarizing-filters#section-best-value | The best polarizing filters | Digital Camera World const headElement = document.querySelectorAll('head')[0]; const BORDEAUX_QUERY_PARAM = 'hybrid_bordeaux_version'; const CHAMPAGNE_QUERY_PARAM = 'hybrid_champagne_version'; const bordeauxScriptTag = document.createElement('script'); bordeauxScriptTag.setAttribute("src", 'https://bordeaux.futurecdn.net/bordeaux.js'); bordeauxScriptTag.setAttribute("onerror", "handleHeaderError()"); bordeauxScriptTag.setAttribute("crossorigin", "anonymous"); bordeauxScriptTag.defer = true; const champagneScriptTag = document.createElement('script'); champagneScriptTag.setAttribute("src", 'https://champagne.futurecdn.net/champagne.js'); champagneScriptTag.setAttribute("onerror", "handleHeaderError()"); champagneScriptTag.setAttribute("crossorigin", "anonymous"); champagneScriptTag.defer = true; const searchParams = new URLSearchParams(window.location.search); const qaBordeauxString = searchParams.get(BORDEAUX_QUERY_PARAM); const qaChampagneString = searchParams.get(CHAMPAGNE_QUERY_PARAM); let adToolVersion = ''; let featureFlags = window.vanilla.featureFlags; let pageType = window.adParameters.type; if (searchParams.has(BORDEAUX_QUERY_PARAM) && qaBordeauxString) { bordeauxScriptTag.setAttribute("src", `https://bdx.${qaBordeauxString}.public.rtb-qa-eks-euw1.futureplc.engineering/bordeaux.js`); adToolVersion = `${qaBordeauxString}`; } if (searchParams.has(CHAMPAGNE_QUERY_PARAM) && qaChampagneString) { champagneScriptTag.setAttribute("src", `https://chmp.${qaChampagneString}.public.rtb-qa-eks-euw1.futureplc.engineering/champagne.js`); } if (window.disableBordeaux === undefined || window.disableBordeaux === false) { headElement.append(bordeauxScriptTag, champagneScriptTag); } window.bordeaux = window.bordeaux || {}; window.bordeaux.cmd = window.bordeaux.cmd || []; window.bordeaux.cmd.push(function () { if (adToolVersion !== '') { window.bordeaux.setAdToolVersion(adToolVersion); } if (window.disableBordeaux === true) { window.bordeaux.setPageTemplate('no-ads'); return; } if (window.dfp_config) { var getDfpVar = function (name) { return window.dfp_config[name] || ''; }; var getDfpList = function (name) { var val = getDfpVar(name); return val ? val.split(',') : []; }; window.bordeaux.setTargeting({ articleid:getDfpVar ('article_id'), pagetype: getDfpList('page_type').join('-'), sitePlatform: getDfpVar ('site_platform'), brand: getDfpVar ('product_brand'), source: getDfpVar ('source'), vertical: getDfpList('vertical'), category: getDfpVar ('category'), child_category: getDfpVar ('child_category'), grandchild_category: getDfpVar ('grandchild_category'), author: getDfpVar ('author'), template: getDfpVar ('template'), jwplayer: Boolean(getDfpVar(' | 2026-01-13T09:29:41 |
https://www.microsoft.com/ko-kr/ai/energy-resources/oil-gas | 석유 및 가스 에너지 솔루션 | Microsoft AI This is the Trace Id: 622221c319b5d69f6da9613bedd4309f 주 콘텐츠로 건너뛰기 Microsoft Microsoft AI Microsoft AI Microsoft AI 홈 제품 및 솔루션 조직용 조직용 Microsoft 365 Copilot Microsoft 365 Copilot 앱 다운로드 조직용 Copilot Agent 365 Customize your Copilot Customize your Copilot Copilot Studio Build your own Build your own Microsoft Foundry Foundry Tools Azure AI 솔루션 파트너 제공 파트너 제공 Microsoft Marketplace Intelligent PCs Intelligent PCs Copilot+ PCs 개인용 개인용 Microsoft Copilot Copilot 앱 다운로드 업계 솔루션 소비재 보안 및 인텔리전스 교육 에너지 및 자원 에너지 및 자원 개요 전력 및 유틸리티 석유 및 가스 채광 금융 서비스 금융 서비스 개요 뱅킹 자본 시장 보험 정부 기관 정부 기관 개요 대중교통 및 도시 인프라 공공 금융 공중 보건 및 복지 서비스 공공 안전 및 정의 의료 서비스 및 생명 과학 의료 서비스 및 생명 과학 개요 공급자 Payors 생명과학 제조 제조 개요 산업 혁신 미디어 및 엔터테인먼트 이동성 이동성 개요 자동차 여행 및 교통 소매 통신 비즈니스 리더를 위한 AI AI 사용 사례 신뢰할 수 있는 AI 책임 있는 AI 책임 있는 AI Microsoft 책임 있는 AI 원칙 및 접근 방식 도구 및 사용 지속 가능성 지속 가능성 지속 가능성 강화 보안 유지 보안 유지 AI 보안 강화 데이터 보호 및 개인 정보 알아보기 AI 101 AI 학습 허브 업계 블로그 Microsoft Cloud 블로그 지원 비즈니스 고객을 위한 지원 산업 문서 자세히 산업 Microsoft for the oil and gas industry</h1> "> 석유 및 가스 산업을 위한 Microsoft 데이터 기반 디지털 솔루션을 사용하여 혁신을 가속화하고, 운영을 최적화하고, 탄소 배출을 줄이세요. 비디오 보기 개요 개요 기능 고객 사례 파트너 제품 리소스 개요 Accelerate the energy transition</h2> "> 에너지 전환 가속화 Microsoft의 신뢰할 수 있는 데이터 및 AI 솔루션을 통해 석유 및 가스 산업에서 더 많은 성과를 달성하세요. 에너지 분야 직원의 역량 강화 원활한 협업을 위해 워크플로를 자동화하고 AI 지원 채용, 학습, 교육을 개선합니다. 새로운 에너지 미래를 추구하는 운영 AI를 사용해 공급망, 보안 자산, 전력 에너지 시스템을 최적화하여 생산성을 높입니다. 넷제로 약속 달성 데이터를 활용하여 탄소 배출을 줄이고, 탄소 없는 에너지의 규모를 늘리고, 에너지 가치 사슬에서 탈탄소를 달성합니다. 지속 가능한 AI 기반 비즈니스 성장 기후 혁신, 지속 가능성 진행률, 비즈니스 성장을 가속화하는 명확한 데이터 인사이트를 얻습니다. 기능 Explore use cases</h2> "> 사용 사례 살펴보기 지속 가능한 미래를 구축하도록 설계된 기술 솔루션을 살펴보세요. 직원 역량 강화 미래형 작업 넷제로 비즈니스 혁신 이전 다음 현장 작업의 디지털화 협업을 강화하고 데이터를 사용하여 실시간 의사 결정을 개선하는 도구를 사용하여 현장 작업자를 더 광범위한 조직에 연결하세요. 기술 향상 사무실 또는 현장에서 일하거나 원격으로 근무하는 직원을 위해 기술 격차를 메우고 대규모로 전문 지식을 구축하는 데 필요한 리소스를 제공하세요. 팀워크 및 협업 분산된 팀을 위해 원격 협업 및 지식 공유를 강화하는 동시에 생산성과 직원 복지를 향상하세요. 생산성 및 프로세스 개선 반복적인 프로세스를 자동화하고 노코드 또는 로우코드 앱으로 솔루션을 맞춤화하여 직원이 더 많은 작업을 수행할 수 있도록 지원하세요. 건강 및 안전 AI 기반 PPE 식별은 물론 모니터링 및 추적 도구를 사용하여 규정 준수를 보장하는 동시에 혼자 일하는 원격 작업자의 안전을 개선합니다. 연결된 작업 및 자산 자산을 연결하고 차세대 AI를 사용하여 예기치 않은 가동 중지 시간을 예측하고 생산을 최적화하며 자율 운영으로 전환하세요. 지능형 공급망 스마트 계약을 가능하게 하고 가시성, 추적성, 순환성을 향상시키는 Just-In-Time AI 지원 공급망 시스템으로 전환합니다. 물리학 기반 모델 지하 처리 및 자산 활용 성과에 대한 계산 효율성과 예측 기능을 개선합니다. 지속 가능한 IT 시스템 고급 분석 및 보고가 가능한 포괄적인 ESG(환경, 사회, 거버넌스) 데이터 자산에서 데이터를 중앙 집중화하고 표준화합니다. ESG 성과 데이터 인텔리전스를 통합하여 환경적 지속성 성과를 모니터링 및 관리하고, 보고를 간소화하고, 보다 효과적인 조치를 취합니다. 지속 가능한 성장 목표를 설정하고, 탄소 발자국을 줄이고, 비즈니스를 혁신하는 데 도움이 되도록 배출 패턴을 포괄적으로 파악합니다. 에너지 효율성 향상 지능형 발전소와 건물을 건설하고, 자산 활용 성과를 최적화하고, 전기화를 가속화합니다. 전기 충전 규모 확장 더욱 스마트해진 충전소를 통해 인프라를 최적화하는 동시에 차량 성능을 개선하고 충전 용량을 늘립니다. 비즈니스 혁신 고객 인사이트를 확보하여 환경을 혁신하고 포트폴리오 다각화 기회를 식별합니다. 지속 가능한 산업의 고도화 Microsoft 기술을 사용하여 탄소 포집, 활용, 저장, 감소 및 배출 시각화를 위한 솔루션을 혁신합니다. 탭으로 돌아가기 고객 사례 See how oil and gas firms are innovating</h2> "> 석유 및 가스 회사의 혁신 방법 보기 이전 슬라이드 다음 슬라이드 "이것은 우리를 디지털화의 다음 차원으로 이끌 기술입니다." Ed Moore, 선임 기술 전략가 제품 HoloLens 2 Dynamics 365 Remote Assist 비디오 보기 "이제 우리 직원은 각자 자신의 요구 사항을 충족하는 맞춤형 로우코드 솔루션을 만들 수 있는 다양한 프로그램에 액세스할 수 있습니다." Javier Espasa, DIY CoE(Center of Excellence) 책임자 €5M 연간 절감액 제품 Power Apps Power Automate 사례 읽기 “우리는 디지털 도구를 통해 탈탄소화 솔루션을 더 빠르고 저렴하게 시장에 출시할 수 있도록 해야 합니다....” Hanne Rolén, 지속 가능성 책임자 제품 Microsoft Cloud for Sustainability Microsoft 환경 크레딧 서비스 사례 읽기 "이 디지털 트윈을 사용하여 과거 데이터를 살펴보고 미래 데이터를 예측함으로써... 우리는 매년 약 500,000톤의 CO 2 등가물 배출량을 줄일 수 있는 기회를 얻었습니다." David Boyd, 시설 공정 엔지니어 제품 Azure 사례 읽기 캐러셀 탐색 컨트롤로 돌아가기 파트너 솔루션 Explore more oil and gas solutions</h2> "> 더 많은 석유 및 가스 솔루션 살펴보기 Microsoft 파트너 에코시스템에서 석유 및 가스 산업 제품을 찾아보세요. 솔루션 살펴보기 이전 슬라이드 다음 슬라이드 DELFI Petrotechnical Suite</h3> "> 석유 기술 작업 흐름 DELFI Petrotechnical Suite AI 및 데이터 분석을 통해 지표 및 지하 작업 흐름을 가속화 및 강화합니다. 자세한 정보 Cognite Data Fusion</h3> "> DataOps Cognite Data Fusion OT/IT 데이터에서 인사이트를 얻어 산업용 AI 솔루션을 개발하고 수익성을 높입니다. 자세한 정보 Kognitwin Simulation by Kongsberg</h3> "> 운영 Kongsberg의 Kognitwin Simulation 역동적이고 안정적인 상태의 클라우드 네이티브 시뮬레이션 기능으로 조직의 역량을 강화하세요. 자세한 정보 BHC3 AI Suite by Baker Hughes C3</h3> "> AI 및 기계 학습 Baker Hughes C3의 BHC3 AI Suite 엔터프라이즈 규모에서 AI, 분석 및 IoT 애플리케이션을 신속하게 개발하고 배포합니다. 자세한 정보 DecisionSpace 365 Digital Well Program</h3> "> 운영 및 공급망 DecisionSpace 365 Digital Well Program 고유한 워크플로 요구 사항을 충족하는 잘 구성된 사용자 지정 프로그램 솔루션을 만듭니다. 자세한 정보 캐러셀 탐색 컨트롤로 돌아가기 제품 Discover products for oil and gas</h2> "> 석유 및 가스 제품 살펴보기 Microsoft의 신뢰할 수 있는 제품을 사용하여 혁신을 가속화하고, 운영을 최적화하고, 탄소 배출량을 줄이세요. 이전 슬라이드 다음 슬라이드 Microsoft Power BI 실시간 데이터 기반 인사이트를 사용하여 지속 가능한 에너지 관리 방식을 개선하고 혁신합니다. 자세한 정보 Microsoft Teams 최전방 직원이 효율적으로 소통하고 협업하는 데 필요한 도구를 제공합니다. 자세한 정보 Dynamics 365 Remote Assist 혼합 현실 기술로 현장 작업자의 역량을 강화하여 더욱 스마트하게 작업할 수 있도록 지원합니다. 자세한 정보 Microsoft Power Platform 모든 팀이 로우코드 도구를 사용하여 솔루션을 개발할 수 있도록 지원하여 비즈니스 전반에서 혁신을 주도합니다. 자세한 정보 Azure Data Manager for Energy 에너지 데이터 관리를 현대화하여 실행 가능한 인사이트를 얻고 운영 효율성을 개선하며 비용을 절감합니다. 자세한 정보 에너지 분야의 Azure IoT 운영 비용을 줄이면서 에너지 관리를 최적화합니다. 자세한 정보 Azure 에너지 생산에서 지능형 그리드까지 작업을 현대화하는 데 도움이 되는 사용자 지정 에너지 솔루션을 구축합니다. 자세한 정보 Dynamics 365 Field Service 기술자에게 최초 문제 해결에 필요한 올바른 정보, 도구, 원격 전문가 지원을 제공합니다. 자세한 정보 Dynamics 365 Customer Service 에너지 서비스를 지원하고 모든 채널에서 뛰어난 고객 서비스를 제공합니다. 자세한 정보 Azure Digital Twins 스마트 공간, 건물, 전력망에 재사용 가능하고 확장성이 뛰어난 환경을 구축합니다. 자세한 정보 배출 영향 대시보드 조직에서 지속 가능한 에너지에 대해 데이터에 기반한 결정을 내리는 데 도움이 되는 중요한 인사이트를 얻으세요. 자세한 정보 캐러셀 탐색 컨트롤로 돌아가기 Explore valuable resources</h2> "> 유용한 리소스 살펴보기 Powering Possible: AI and Energy for a Sustainable Future</h3> "> 보고서 • 2024년 10월 가능한 기능: 지속 가능한 미래를 위한 AI와 에너지 AI가 글로벌 에너지 부문을 어떻게 탄소중립으로 이끌 수 있는지 살펴보세요. 보고서 가져오기 Explore the benefits of cloud migration in the energy industry</h3> "> 인포그래픽 • 2023년 1월 에너지 산업에서 클라우드 마이그레이션의 이점 살펴보기 인포그래픽 다운로드 Learn about the Energy Transition Center of Excellence</h3> "> 개요 • 2023 에너지 전환 CoE(Center of Excellence)에 대해 자세히 알아보기 개요 보기 Learn how to power a sustainable energy future</h3> "> 블로그 지속 가능한 에너지 미래를 만드는 방법 알아보기 블로그 살펴보기 다음 단계 Achieve more in the energy industry</h2> "> 에너지 산업에서 더 많은 성과 달성하기 비즈니스 솔루션 허브 클라우드 솔루션 찾기 귀사의 고유한 비즈니스 목표에 적합한 솔루션을 찾으려면 지금 살펴보세요. 모든 솔루션 살펴보기 Microsoft AI AI로 더욱 지속 가능한 미래 구축 AI 기반 솔루션을 통해 에너지 및 리소스 산업을 재창조하고 넷 제로를 달성하세요. 자세한 정보 팔로우하기 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 | 2026-01-13T09:29:41 |
https://www.atlassian.com/pl/legal/cloud-terms-of-service | Atlassian Customer Agreement | Atlassian Close Czy wyświetlić tę stronę w Twoim języku ? Wszystkie języki Wybierz swój język 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Zacznij korzystać za darmo Produkty Polecane Programiści Menedżerowie produktu Specjaliści IT Zespoły biznesowe Kadra zarządzająca Polecane Programiści Menedżerowie produktu Specjaliści IT Zespoły biznesowe Kadra zarządzająca Wyświetl wszystkie aplikacje Polecane Polecane aplikacje Jira Elastyczne zarządzanie projektami Confluence Wspólna przestrzeń robocza wiedzy Jira Service Management Dostarczanie usług z dużą prędkością ATLASSIAN COLLECTIONS Płynne usprawnienie pracy zespołowej Jira • Confluence • Loom • Rovo Pewna optymalizacja strategii i wyników Focus • Talent • Align Szybkie świadczenie usług Jira Service Management • Customer Service Management • Zasoby • Rovo Szybkie dostarczanie oprogramowania wysokiej jakości Rovo Dev • DX • Pipelines • Bitbucket • Compass Obsługiwane przez Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Programiści Jira Elastyczne zarządzanie projektami Compass Katalog oprogramowania dla zespołów Procesy organizacji produkcji Skalowalna automatyzacja CI/CD Bitbucket Kod źródłowy i CI/CD DX (W oczekiwaniu na przejęcie) Mierz wydajność oraz wpływ sztucznej inteligencji Rovo Dev Oparte na sztucznej inteligencji agenty dla programistów Szybkie dostarczanie oprogramowania wysokiej jakości Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Menedżerowie produktu Jira Elastyczne zarządzanie projektami Confluence Wiedza, wszystkie informacje w jednym miejscu Jira Product Discovery NOWOŚĆ Rejestrowanie pomysłów i nadawanie im priorytetów Płynne usprawnienie pracy zespołowej Jira • Confluence • Loom • Rovo Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Specjaliści IT Jira Service Management Dostarczanie usług z dużą prędkością Guard NOWOŚĆ Zwiększone bezpieczeństwo w chmurze Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Zespoły biznesowe Jira Elastyczne zarządzanie projektami Confluence Wiedza, wszystkie informacje w jednym miejscu Trello Porządkowanie i wizualizowanie pracy Loom NOWOŚĆ Szybkie, asynchroniczne aktualizacje wideo Jira Service Management Dostarczanie usług z dużą prędkością Customer Service Management Customer experiences reimagined Płynne usprawnienie pracy zespołowej Jira • Confluence • Loom • Rovo Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Kadra zarządzająca Focus NOWOŚĆ Planowanie strategiczne w skali przedsiębiorstwa Talent NOWOŚĆ Planowanie zasobów ludzkich pod kątem wiedzy Jira Align Znaczenie i planowanie pracy w całym przedsiębiorstwie Pewna optymalizacja strategii i wyników Focus • Talent • Align Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Back Rozwiązania Rozwiązania Według przypadku użycia Współpraca zespołowa Strategia i planowanie Zarządzanie usługami Tworzenie oprogramowania Według zespołu Oprogramowanie Marketing IT Według rozmiaru Enterprise Małe firmy Startup Organizacje non-profit Według branży Handel detaliczny Telekomunikacja Usługi specjalistyczne Administracja publiczna Rovo Aplikacje oparte na sztucznej inteligencji napędzane wiedzą Twojego zespołu. Back Dlaczego Atlassian Dlaczego Atlassian System pracy Nowość Plan Atlassian dotyczący współpracy zespołów Narzędzia Integracji Tysiące aplikacji do połączenia z produktami Atlassian Klienci Studia przypadków i historyjki oparte na pracy zespołowej FedRAMP Zgodne rozwiązania dla sektora publicznego Odporność Wysoce wydajna struktura klasy korporacyjnej Platforma Nasza głęboko zintegrowana, niezawodna i bezpieczna platforma Centrum zaufania Bezpieczeństwo danych, zgodność z przepisami i dostępność Back Zasoby Zasoby Obsługa klienta Zadawaj pytania, zgłaszaj błędy i dziel się opinią Znajdź partnerów Skorzystaj z doradztwa, szkolenia i wsparcia w zakresie dostosowywania produktów Atlassian Ascend Zasoby i wsparcie ułatwiające transformację Społeczność Ucz się, łącz i rozwijaj ze społecznością Atlassian Wsparcie Pytania ogólne Doradztwo dotyczące produktu Wsparcie dla partnerów Wsparcie dla firm Wsparcie techniczne Ceny i płatności Wsparcie dla programistów Zakup licencji Zasoby Zarządzanie projektami Agile Atlassian Learning Rozpocznij korzystanie Współpraca nad projektem Podręcznik Team Playbook Dokumentacja produktu Back Enterprise Więcej + Mniej - Zacznij korzystać za darmo Jira Elastyczne zarządzanie projektami Jira Service Management Dostarczanie usług z dużą prędkością Confluence Wiedza, wszystkie informacje w jednym miejscu Zobacz wszystkie produkty Zacznij korzystać za darmo Back Zacznij korzystać za darmo Legal Legal information Atlassian Customer Agreement Atlassian Customer Agreement Atlassian provides a wide range of products, services, and deployment options. As part of our dedication to building with heart and balance, we have developed the Atlassian Customer Agreement to encompass all these offerings in a comprehensive and customized manner. Our products adhere to an enterprise-level set of controls and policies that align with various international standards and market expectations. The agreement is crafted to be customer-friendly, undergoing regular updates informed by market practices and customer input. For further insight into our approach, please visit this page . Atlassian Customer Agreement Download PDF Effective starting: October 15, 2024 This Agreement is between Customer and Atlassian. “ Customer ” means the entity on behalf of which this Agreement is accepted or, if that does not apply, the individual accepting this Agreement. “ Atlassian ” means the Atlassian entity that owns or operates the Products that Customer uses or accesses listed at https://www.atlassian.com/legal/product-terms. If you (the person accepting this Agreement) are accepting this Agreement on behalf of your employer or another entity, you agree that: (i) you have full legal authority to bind your employer or such entity to this Agreement, and (ii) you agree to this Agreement on behalf of your employer or such entity. If you are accepting this Agreement using an email address from your employer or another entity, then: (i) you will be deemed to represent that party, (ii) your acceptance of this Agreement will bind your employer or that entity to these terms, and (iii) the word “you” or “Customer” in this Agreement will refer to your employer or that entity. By clicking on the “Agree” (or similar button or checkbox) that is presented to you at the time of placing an Order, downloading Products, or by using or accessing the Products, you confirm you are bound by this Agreement. If you do not wish to be bound by this Agreement, do not click “Agree” (or similar button or checkbox), download the Products, or use or access the Products. 1. Overview This Agreement applies to Customer’s Orders for Products and related Support and Advisory Services. The terms of this Agreement apply to both Cloud Products and Software Products, although certain terms apply only to Cloud Products or Software Products, as specified below. In addition, some Products are subject to additional Product-Specific Terms, and Support and Advisory Services are subject to the applicable Policies. 2. Use of Products 2.1. Permitted Use . Subject to this Agreement and during the applicable Subscription Term, Atlassian grants Customer a non-exclusive, worldwide right to use the Products and related Support and Advisory Services for its and its Affiliates’ internal business purposes, in accordance with the Documentation and subject to Customer’s Scope of Use, as specified in the Order and the Product-Specific Terms. 2.2. Restrictions . Except to the extent otherwise expressly permitted by this Agreement, Customer must not (and must not permit anyone else to): (a) rent, lease, sell, distribute or sublicense the Products or (except for Affiliates) include them in a service bureau or outsourcing offering, (b) provide access to the Products to a third party, other than to Users, (c) charge its customers a specific fee for use of the Products, but Customer may charge an overall fee for its own offerings (of which the Products are ancillary), (d) use the Products to develop a similar or competing product or service, (e) reverse engineer, decompile, disassemble or seek to access the source code or non-public APIs to the Products, (f) modify or create derivative works of the Products, (g) interfere with or circumvent Product usage limits or Scope of Use restrictions, (h) remove, obscure or modify in any way any proprietary or other notices or attributions in the Products, or (i) violate the Acceptable Use Policy. 2.3. DPA . The DPA applies to Customer’s use of Products and related Support and Advisory Services and forms part of this Agreement. 3. Users 3.1. Responsibility . Customer may authorize Users to access and use the Products, in accordance with the Documentation and Customer’s Scope of Use. Customer is responsible for its Users’ compliance with this Agreement and all activities of its Users, including Orders they may place, apps and Third Party-Products enabled, and how Users access and use Customer Data. 3.2. Login Credentials . Customer must ensure that each User keeps its login credentials confidential and must promptly notify Atlassian if it becomes aware of any unauthorized access to any User login credentials or other unauthorized access to or use of the Products. 3.3. Domain Ownership . Where a Cloud Product requires Customer to specify a domain (such as www.example.com ) for the Cloud Product’s or a feature’s operation, Atlassian may verify that Customer or an Affiliate owns or controls that domain. Atlassian has no obligation to provide that Cloud Product or feature if Atlassian cannot verify that Customer or an Affiliate owns or controls the domain. Product administrators appointed by Customer may also take over management of accounts previously registered using an email address belonging to Customer’s domain, which become “managed accounts” (or similar term), as described in the Documentation 3.4. Age Requirements . The Products are not intended for use by anyone under the age of 16. Customer is responsible for ensuring that all Users are at least 16 years old. 4. Cloud Products This Section 4 only applies to Cloud Products. 4.1. Customer Data . Atlassian may process Customer Data to provide the Cloud Products and related Support or Advisory Services in accordance with this Agreement. 4.2. Security Program . Atlassian has implemented and will maintain an information security program that uses appropriate physical, technical and organizational measures designed to protect Customer Data from unauthorized access, destruction, use, modification or disclosure, as described in its Security Measures. Atlassian will also maintain a compliance program that includes independent third-party audits and certifications, as described in its Security Measures. Further information about Atlassian’s security program is available on the Atlassian Trust Center at https://www.atlassian.com/trust , as updated from time to time. 4.3. Service Levels . Where applicable, service level commitments for the Cloud Products are set out in the Service Level Agreement. 4.4. Data Retrieval . The Documentation describes how Customer may retrieve its Customer Data from the Cloud Products. 4.5. Removals and Suspension . Atlassian has no obligation to monitor Customer Data. Nonetheless, if Atlassian becomes aware that: (a) Customer Data may violate Law, Section 2.2 (Restrictions), or the rights of others (including relating to a takedown request received following the guidelines for Reporting Copyright and Trademark Violations at https://www.atlassian.com/legal/copyright-and-trademark-violations ), or (b) Customer’s use of the Cloud Products threatens the security or operation of the Cloud Products, then Atlassian may: (i) limit access to, or remove, the relevant Customer Data, or (ii) suspend Customer’s or any User’s access to the relevant Cloud Products. Atlassian may also take any such measures where required by Law, or at the request of a governmental authority. When practicable, Atlassian will give Customer the opportunity to remedy the issue before taking any such measures. 5. Software Products This Section 5 only applies to Software Products. 5.1. Modifications . Atlassian may provide some portions of the Software Products in source code form for Customer to use internally to create bug fixes, configurations or other modifications of the Software Products, as permitted in the Documentation (“ Modifications ”). Customer must keep such source code secure (on computer devices and online repositories controlled by Customer), confidential, and only make it available to Customer’s employees who have a legitimate need to access and use the source code to create and maintain Modifications. Customer may only use Modifications with the Software Products, and only in accordance with this Agreement, including the Third-Party Code Policy, the Documentation, and Customer’s Scope of Use. Customer must not distribute source code or Modifications to third parties. Customer must securely destroy the source code at the earliest of: (a) Customer no longer needing to use source code to create or maintain Modifications, (b) termination or non-renewal of a relevant Subscription Term, or (c) Atlassian’s request for any reason. Notwithstanding anything else in this Agreement, Atlassian has no support, warranty, indemnity or other responsibility for Modifications. 5.2. License Verification . Upon Atlassian’s written request, Customer will promptly confirm in writing whether its use of the Software Products is in compliance with the applicable Scope of Use. Atlassian or its authorized agents may audit Customer’s use of the Software Products no more than once every twelve (12) months to confirm compliance with Customer’s Scope of Use, provided Atlassian gives Customer reasonable advance notice and uses reasonable efforts to minimize disruption to Customer. If Customer exceeds its Scope of Use, Atlassian may invoice for that excess use, and Customer will pay Atlassian promptly after invoice receipt. 5.3. Number of Instances . Unless otherwise specified in the Order or the Product-Specific Terms, Customer may install up to one (1) production instance of each Software Product included in an Order on systems owned or operated by Customer or its Users. 6. Customer Obligations 6.1. Disclosures and Rights . Customer must ensure it has made all disclosures and obtained all rights and consents necessary for Atlassian to use Customer Data and Customer Materials to provide the Cloud Products, Support or Advisory Services. 6.2. Product Assessment . Customer is responsible for determining whether the Products meet Customer’s requirements and any regulatory obligations related to its intended use. 6.3. Sensitive Health Information and HIPAA . Unless the parties have entered into a ‘Business Associate Agreement,’ Customer must not (and must not permit anyone else to) upload to the Cloud Products (or use the Cloud Products to process) any patient, medical or other protected health information regulated by the Health Insurance Portability and Accountability Act. 7. Third-Party Code and Third-Party Products 7.1. Third-Party Code . This Agreement and the Third-Party Code Policy apply to open source software and commercial third-party software Atlassian includes in the Products. 7.2. Third-Party Products . Customer may choose to use the Products with third-party platforms, apps, add-ons, services or products, including offerings made available through the Atlassian Marketplace (“ Third-Party Products ”). Use of such Third-Party Products with the Products may require access to Customer Data and other data by the third-party provider, which, for Cloud Products Atlassian will permit on Customer’s behalf if Customer has enabled that Third-Party Product. Customer’s use of Third-Party Products is subject to the relevant provider’s terms of use, not this Agreement. Atlassian does not control and has no liability for Third-Party Products. 8. Support and Advisory Services Atlassian will provide Support and Advisory Services as described in the Order and applicable Policies. Atlassian’s provision of Support or Advisory Services is subject to Customer providing timely access to Customer Materials and personnel reasonably requested by Atlassian. 9. Ordering Process and Delivery No Order is binding until Atlassian provides its acceptance, including by sending a confirmation email, providing access to the Products, or making license or access keys available to Customer. No terms of any purchase order or other business form used by Customer will supersede, supplement, or otherwise apply to this Agreement or Atlassian. Atlassian will deliver login instructions or license keys for Products electronically, to Customer’s account (or through other reasonable means) promptly upon receiving payment of the fees. Customer is responsible for the installation of Software Products, and Atlassian has no further delivery obligations with respect to the Software Products after delivery of license keys. 10. Billing and Payment 10.1. Fees . (a) Direct Purchases . If Customer purchases directly from Atlassian, fees and any payment terms are specified in Customer’s Order with Atlassian. (b) Resellers . If Customer purchases through a Reseller, Customer must pay all applicable amounts directly to the Reseller, and Customer’s order details (e.g., Products and Scope of Use) will be specified in the Order placed by the Reseller with Atlassian on Customer’s behalf. (c) Renewals . Unless otherwise specified in an Order and subject to the Product, Support or Advisory Services continuing to be generally available, a Subscription Term will automatically renew at Atlassian’s then current rates for: (i) if Customer’s prior Subscription was for a period less than twelve (12) months, another Subscription Term of a period equal to Customer’s prior Subscription Term, or (ii) if Customer’s prior Subscription Team was for twelve (12) months or more, twelve (12) months. Either party may elect not to renew a Subscription Term by giving notice to the other party before the end of the current Subscription Term. Customer must provide any notice of non-renewal through account settings in the Products, by contacting Atlassian’s support team or by otherwise providing Atlassian notice. (d) Increased Scope of Use . If Customer exceeds the Scope of Use purchased, unless otherwise agreed with Atlassian in writing, Customer must upgrade its subscription or pay for the increased Scope of Use. Unless otherwise specified in an applicable Order, Atlassian will charge Customer for any increased Scope of Use at Atlassian’s then-current rates, which may be prorated for the remainder of the then-current Subscription Term. (e) Refunds . All fees and expenses are non-refundable, except as otherwise provided in this Agreement. For any purchases Customer makes through a Reseller, any refunds from Atlassian payable to Customer relating to that purchase will be remitted by that Reseller, unless Atlassian specifically notifies Customer otherwise at the time of refund. (f) Credit Cards . If Customer uses a credit card or similar online payment method for its initial Order, then Atlassian may bill that payment method for renewals, additional Orders, overages to scopes of use, expenses, and unpaid fees, as applicable. 10.2. Taxes . (a) Taxes Generally . Fees and expenses are exclusive of any sales, use, GST, value-added, withholding or similar taxes or levies that apply to Customer’s Orders. Other than taxes on Atlassian’s net income, Customer is responsible for any such taxes or levies and must pay those taxes or levies, which Atlassian will itemize separately, in accordance with an applicable invoice. (b) Withholding Taxes . To the extent Customer is required to withhold tax from payment to Atlassian in certain jurisdictions, Customer must provide valid documentation it receives from the taxing authority in such jurisdictions confirming remittance of withholding. This documentation must be provided at the time of payment of the applicable invoice to Atlassian. (c) Exemptions . If Customer claims exemption from any sales tax, VAT, GST or similar taxes under this Agreement, Customer must provide Atlassian a valid tax exemption certificate or tax ID at the time of Order, and after receipt of valid evidence of exemption, Atlassian will not include applicable taxes on the relevant Customer invoice. 10.3. Return Policy . Within thirty (30) days of its initial Order for a Product, Customer may terminate the Subscription Term for that Product, for any or no reason, by providing notice to Atlassian. Following such termination, upon request (which may be made through Customer’s Atlassian account), Atlassian will refund Customer the amount paid for that Product and any associated Support under the applicable Order. Unless otherwise specified in the Policies or Product-Specific Terms, this return policy does not apply to Advisory Services. 10.4. Suspension for Non-payment . Atlassian may suspend Customer’s rights to use Products or receive Support or Advisory Services if payment is overdue, and Atlassian has given Customer no fewer than ten (10) days’ written notice. 11. Atlassian Warranties 11.1. Performance Warranties . Atlassian warrants to Customer that: (a) the Products will operate in substantial conformity with the applicable Documentation during the applicable Subscription Term, (b) Atlassian will not materially decrease the functionality or overall security of the Products during the applicable Subscription Term, and (c) Atlassian will use reasonable efforts designed to ensure that the Products, when and as provided by Atlassian, are free of any viruses, malware or similar malicious code (each, a “ Performance Warranty ”). 11.2. Performance Warranty Remedy . If Atlassian breaches a Performance Warranty and Customer makes a reasonably detailed warranty claim within 30 days of discovering the issue, Atlassian will use reasonable efforts to correct the non-conformity. If Atlassian determines such remedy to be impracticable, either party may terminate the affected Subscription Term. Atlassian will then refund to Customer any pre-paid, unused fees for the terminated portion of the Subscription Term. These procedures are Customer’s exclusive remedy and Atlassian’s entire liability for breach of a Performance Warranty. 11.3. Exclusions . The warranties in this Section 11 (Atlassian Warranties) do not apply to: (a) the extent the issue or non-conformity is caused by Customer’s unauthorized use or modification of the Products, (b) unsupported releases of Software Products or Cloud Clients, or (c) Third-Party Products. 11.4. Disclaimers . Except as expressly provided in this Section 11 (Atlassian Warranties), the Products, Support and Advisory Services and all related Atlassian services and deliverables are provided “AS IS.” Atlassian makes no other warranties, whether express, implied, statutory or otherwise, including warranties of merchantability, fitness for a particular purpose, title or non-infringement. Atlassian does not warrant that Customer’s use of the Products will be uninterrupted or error-free. Atlassian is not liable for delays, failures or problems inherent in use of the internet and electronic communications or other systems outside Atlassian’s control. 12. Term and Termination 12.1. Term . This Agreement commences on the date Customer accepts it and expires when all Subscription Terms have ended. 12.2. Termination for Convenience . Customer may terminate this Agreement or a Subscription Term upon notice for any reason. Subject to Section 10.3 (Return Policy), Customer will not be entitled to any refunds as a result of exercising its rights under this Section 12.2, and any unpaid amounts for the then-current Subscription Terms and any related service periods will become due and payable immediately upon such termination. 12.3. Termination for Cause . Either party may terminate this Agreement or a Subscription Term if the other party: (a) fails to cure a material breach of this Agreement (including a failure to pay fees) within 30 days after notice, (b) ceases operation without a successor, or (c) seeks protection under a bankruptcy, receivership, trust deed, creditors’ arrangement, composition or comparable proceeding, or if such a proceeding is instituted against that party and not dismissed within 60 days. If Customer terminates this Agreement or a Subscription Term in accordance with this Section 12.3, Atlassian will refund to Customer any pre-paid, unused fees for the terminated portion of the Agreement or applicable Subscription Term. 12.4. Effect of Termination . Upon expiration or termination of this Agreement or a Subscription Term: (a) Customer’s rights to use the applicable Products, Support or Advisory Services will cease, (b) Customer must immediately cease accessing the Cloud Products and using the applicable Software Products and Cloud Clients, and (c) Customer must delete (or, on request, return) all license keys, access keys and any Product copies. Following expiration or termination, unless prohibited by Law, Atlassian will delete Customer Data in accordance with the Documentation. 12.5. Survival . These Sections survive expiration or termination of this Agreement: 2.2 (Restrictions), 4.2 (Security Program), 10.1 (Fees), 10.2 (Taxes), 11.4 (Disclaimers), 12.4 (Effect of Termination), 12.5 (Survival), 13 (Ownership), 14 (Limitations of Liability), 15 (Indemnification by Atlassian), 16 (Confidentiality), 17.4 (Disclaimer), 18 (Feedback), 20 (General Terms) and 21 (Definitions). 13. Ownership Except as expressly set out in this Agreement, neither party grants the other any rights or licenses to its intellectual property under this Agreement. As between the parties, Customer owns all intellectual property and other rights in Customer Data and Customer Materials provided to Atlassian or used with the Products. Atlassian and its licensors retain all intellectual property and other rights in the Products, any Support and Advisory Services deliverables and related source code, Atlassian technology, templates, formats and dashboards, including any modifications or improvements. 14. Limitations of Liability 14.1. Damages Waiver . Except for Excluded Claims or Special Claims, to the maximum extent permitted by Law, neither party will have any liability arising out of or related to this Agreement for any loss of use, lost data, lost profits, interruption of business or any indirect, special, incidental, reliance or consequential damages of any kind, even if informed of their possibility in advance. 14.2. General Liability Cap . Except for Excluded Claims or Special Claims, to the maximum extent permitted by Law, each party’s entire liability arising out of or related to this Agreement will not exceed in aggregate the amounts paid to Atlassian for the Products, Support and Advisory Services giving rise to the liability during the twelve (12) months preceding the first event out of which the liability arose. Customer’s payment obligations under Sections 10.1 (Fees) and 10.2 (Taxes) are not limited by this Section 14.2. 14.3. Excluded Claims . “ Excluded Claims ” means: (a) Customer’s breach of Section 2.2 (Restrictions) or Section 6 (Customer Obligations), (b) either party’s breach of Section 16 (Confidentiality) but excluding claims relating to Customer Data or Customer Materials, or (c) amounts payable to third parties under Atlassian’s obligations in Section 15 (Indemnification by Atlassian). 14.4. Special Claims . For Special Claims, Atlassian’s aggregate liability under this Agreement will be the lesser of: (a) two times (2x) the amounts paid to Atlassian for the Products, Support and Advisory Services giving rise to the Special Claim during the twelve (12) months preceding the first event out of which the Special Claim arose, and (b) US$5,000,000. “ Special Claims ” means any unauthorized disclosure of Customer Data or Customer Materials caused by a breach by Atlassian of its obligations in Section 4.2 (Security Program). 14.5. Nature of Claims and Failure of Essential Purpose . The exclusions and limitations in this Section 14 (Limitations of Liability) apply regardless of the form of action, whether in contract, tort (including negligence), strict liability or otherwise and will survive and apply even if any limited remedy in this Agreement fails of its essential purpose. 15. Indemnification by Atlassian 15.1. IP Indemnification . Atlassian must: (a) defend Customer from and against any third-party claim to the extent alleging that the Products, when used by Customer as authorized by this Agreement, infringe any intellectual property right of a third party (an “ Infringement Claim ”), and (b) indemnify and hold harmless Customer against any damages, fines or costs finally awarded by a court of competent jurisdiction (including reasonable attorneys’ fees) or agreed in settlement by Atlassian resulting from an Infringement Claim. 15.2. Procedures . Atlassian’s obligations in Section 15.1 (IP Indemnification) are subject to Customer providing: (a) sufficient notice of the Infringement Claim so as to not prejudice Atlassian’s defense of the Infringement Claim, (b) the exclusive right to control and direct the investigation, defense and settlement of the Infringement Claim, and (c) all reasonably requested cooperation, at Atlassian’s expense for reasonable out-of-pocket expenses. Customer may participate in the defense of an Infringement Claim with its own counsel at its own expense. 15.3. Settlement . Customer may not settle an Infringement Claim without Atlassian’s prior written consent. Atlassian may not settle an Infringement Claim without Customer’s prior written consent if settlement would require Customer to admit fault or take or refrain from taking any action (other than relating to use of the Products). 15.4. Mitigation . In response to an actual or potential Infringement Claim, Atlassian may, at its option: (a) procure rights for Customer’s continued use of the Products, (b) replace or modify the alleged infringing portion of the Products without reducing the overall functionality of the Products, or (c) terminate the affected Subscription Term and refund to Customer any pre-paid, unused fees for the terminated portion of the Subscription Term. 15.5. Exceptions . Atlassian’s obligations in this Section 15 (Indemnification by Atlassian) do not apply to the extent an Infringement Claim arises from: (a) Customer’s modification or unauthorized use of the Products, (b) use of the Products in combination with items not provided by Atlassian (including Third-Party Products), (c) any unsupported release of the Software Products or Cloud Clients, or (d) Third-Party Products, Customer Data or Customer Materials. 15.6. Exclusive Remedy . This Section 15 (Indemnification by Atlassian) sets out Customer’s exclusive remedy and Atlassian’s entire liability regarding infringement of third-party intellectual property rights. 16. Confidentiality. 16.1. Definition . “ Confidential Information ” means information disclosed by one party to the other under or in connection with this Agreement that: (a) is designated by the disclosing party as proprietary or confidential, or (b) should be reasonably understood to be proprietary or confidential due to its nature and the circumstances of its disclosure. Atlassian’s Confidential Information includes any source code and technical or performance information about the Products. Customer’s Confidential Information includes Customer Data and Customer Materials. 16.2. Obligations . Unless expressly permitted by the disclosing party in writing, the receiving party must: (a) hold the disclosing party’s Confidential Information in confidence and not disclose it to third parties except as permitted in this Agreement, and (b) only use such Confidential Information to fulfill its obligations and exercise its rights in this Agreement. The receiving party may disclose such Confidential Information to its employees, agents, contractors and other representatives having a legitimate need to know (including, for Atlassian, the subcontractors referenced in Section 20.11 (Subcontractors and Affiliates)), provided the receiving party remains responsible for their compliance with this Section 16 (Confidentiality) and they are bound to confidentiality obligations no less protective than this Section 16 (Confidentiality). 16.3. Exclusions . These confidentiality obligations do not apply to information that the receiving party can demonstrate: (a) is or becomes publicly available through no fault of the receiving party, (b) it knew or possessed prior to receipt under this Agreement without breach of confidentiality obligations, (c) it received from a third party without breach of confidentiality obligations, or (d) it independently developed without using the disclosing party’s Confidential Information. The receiving party may disclose Confidential Information if required by Law, subpoena or court order, provided (if permitted by Law) it notifies the disclosing party in advance and cooperates, at the disclosing party’s cost, in any reasonable effort to obtain confidential treatment. 16.4. Remedies . Unauthorized use or disclosure of Confidential Information may cause substantial harm for which damages alone are an insufficient remedy. Each party may seek appropriate equitable relief, in addition to other available remedies, for breach or anticipated breach of this Section 16 (Confidentiality). 17. Free or Beta Products 17.1. Access . Customer may receive access to certain Products or Product features on a free, fully discounted or trial basis, or as an alpha, beta or early access offering (“ Free or Beta Products ”). Use of Free or Beta Products is subject to this Agreement and any additional terms specified by Atlassian, such as the applicable scope and term of use. 17.2. Termination or Modification . At any time, Atlassian may terminate or modify Customer’s use of (including applicable terms) Free or Beta Products or modify Free or Beta Products, without any liability to Customer. For modifications to Free or Beta Products or Customer’s use, Customer must accept those modifications to continue accessing or using the Free or Beta Products. 17.3. Pre GA . Free or Beta Products may be inoperable, incomplete or include errors and bugs or features that Atlassian may never release, and their features and performance information are Atlassian’s Confidential Information. 17.4. Disclaimer . Notwithstanding anything else in this Agreement, to the maximum extent permitted by Law, Atlassian provides no warranty, indemnity, service level agreement or support for Free or Beta Products and its aggregate liability for Free or Beta Products is limited to US$100. 18. Feedback If Customer provides Atlassian with feedback or suggestions regarding the Products or other Atlassian offerings, Atlassian may use the feedback or suggestions without restriction or obligation. 19. Publicity Atlassian may identify Customer as a customer of Atlassian in its promotional materials. Atlassian will promptly stop doing so upon Customer request . 20. General Terms 20.1. Compliance with Laws . Each party must comply with all Laws applicable to its business in its performance of obligations or exercise of rights under this Agreement. 20.2. Code of Conduct . Atlassian must comply with its Code of Conduct in its performance of obligations or exercise of rights under this Agreement. 20.3. Assignment . (a) Customer may not assign or transfer any of its rights or obligations under this Agreement or an Order without Atlassian’s prior written consent. However, Customer may assign this Agreement in its entirety (including all Orders) to its successor resulting from a merger, acquisition, or sale of all or substantially all of Customer’s assets or voting securities, provided that Customer provides Atlassian with prompt written notice of the assignment and the assignee agrees in writing to assume all of Customer’s obligations under this Agreement and complies with Atlassian’s procedural and documentation requirements to give effect to the assignment. (b) Any attempt by Customer to transfer or assign this Agreement or an Order, except as expressly authorized above, will be null and void. (c) Atlassian may assign its rights and obligations under this Agreement (in whole or in part) without Customer’s consent. 20.4. Governing Law, Jurisdiction and Venue . (a) If Customer is domiciled: (i) in Europe, the Middle East, or Africa, this Agreement is governed by the laws of the Republic of Ireland, with the jurisdiction and venue for actions related to this Agreement in the courts of the Republic of Ireland, or (ii) elsewhere, this Agreement is governed by the laws of the State of California, with the jurisdiction and venue for actions related to this Agreement in the state and United States federal courts located in San Francisco, California. (b) This Agreement will be governed by such laws without regard to conflicts of laws provisions, and both parties submit to the personal jurisdiction of the applicable courts. The United Nations Convention on the International Sale of Goods does not apply to this Agreement. 20.5. Notices . (a) Except as specified elsewhere in this Agreement, notices under this Agreement must be in writing and are deemed given on: (i) personal delivery, (ii) when received by the addressee if sent by a recognized overnight courier with receipt request, (iii) the third business day after mailing, or (iv) the first business day after sending by email, except that email will not be sufficient for notices regarding Infringement Claims, alleging breach of this Agreement by Atlassian, or of Customer’s termination of this Agreement in accordance with Section 12.3 (Termination for Cause). (b) Notices to Atlassian must be provided according to the details provided at https://www.atlassian.com/legal#how-do-i-provide-legal-notices-to-atlassian , as may be updated from time to time (c) Notices to Customer must be provided to the billing or technical contact provided to Atlassian, which may be updated by Customer from time to time in Customer’s account portal. However, Atlassian may provide general or operational notices via email, on its website or through the Products. Customer may subscribe to receive email notice of updates to this Agreement, as described at https://www.atlassian.com/legal#notification-of-updates-in-terms-and-policies . 20.6. Entire Agreement . This Agreement is the parties’ entire agreement regarding its subject matter and supersedes any prior or contemporaneous agreements regarding its subject matter. In the event of a conflict among the documents making up this Agreement, the main body of this Agreement (i.e., Sections 1 through 21, inclusive) will control, except that the Policies, Product-Specific Terms and DPA will control for their specific subject matter. 20.7. Other Atlassian Offerings . Atlassian makes available other offerings that can be used with the Products which, in some cases, are subject to separate terms and conditions, available at https://www.atlassian.com/legal . These other offerings include training services, developer tools and the Atlassian Marketplace. For clarity, this Agreement controls over any such terms and conditions with respect to Customer’s use of the Products (including any Atlassian Apps). 20.8. Interpretation, Waivers and Severability . In this Agreement, headings are for convenience only and “including” and similar terms are to be construed without limitation. Waivers must be granted in writing and signed by the waiving party’s authorized representative. If any provision of this Agreement is held invalid, illegal or unenforceable, it will be limited to the minimum extent necessary so the rest of this Agreement remains in effect. 20.9. Changes to this Agreement . (a) Atlassian may modify this Agreement (which includes the Policies, Product-Specific Terms and DPA) from time to time, by posting the modified portion(s) of this Agreement on Atlassian’s website. Atlassian must use commercially reasonable efforts to post any such modification at least thirty (30) days prior to its effective date. (b) For free subscriptions, modifications become effective during the then current Subscription Term, in accordance with Atlassian’s notice. (c) For paid subscriptions: (i) except as specified below, modifications to this Agreement will take effect at the next Order or renewal unless either party elects to not renew pursuant to Section 10.1(c) (Renewals), and (ii) Atlassian may specify that modifications will become effective during a then-current Subscription Term if: (A) required to address compliance with Law, or (B) required to reflect updates to Product functionality or introduction of new Product features. If Customer objects, Customer may terminate the remainder of the then-current Subscription Term for the affected Products as its exclusive remedy. To exercise this right, Customer must notify Atlassian of its termination under this Section 20.9(c) within thirty (30) days of the modification notice, and Atlassian will refund any pre-paid fees for the terminated portion of the applicable Subscription Term. 20.10. Force Majeure . Neither party is liable for any delay or failure to perform any obligation under this Agreement (except for a failure to pay fees) due to events beyond its reasonable control and occurring without that party’s fault or negligence. 20.11. Subcontractors and Affiliates . Atlassian may use subcontractors or its Affiliates in the performance of its obligations under this Agreement, but Atlassian remains responsible for its overall performance under this Agreement and for having appropriate written agreements in place with its subcontractors to enable Atlassian to meet its obligations under this Agreement. 20.12. Independent Contractors . The parties are independent contractors, not agents, partners or joint venturers. 20.13. Export Restrictions . The Products may be subject to U.S. export restrictions and import restrictions of other jurisdictions. Customer must comply with all applicable export and import Laws in its access to, use of, and download of the Products or any content or records entered into the Products. Customer must not (and must not allow anyone else to) export, re-export, transfer or disclose the Products or any direct product of the Products: (a) to (or to a national or resident of) any U.S. embargoed jurisdiction, (b) to anyone on any U.S. or applicable non-U.S. restricted- or denied-party list, or (c) to any party that Customer has reason to know will use the Products in violation of U.S. export Law, or for any restricted end user under U.S. export Law. 20.14. Government End-Users . If Customer is a United States federal, state or local government customer, this Agreement is subject to, and is varied by, the Government Amendment available at https://www.atlassian.com/legal/government-amendment . 20.15. No Contingencies . The Products, Support and Advisory Services in each Order are purchased separately and not contingent on purchase or use of other Atlassian products and services, even if listed in the same Order. Customer’s purchases are not contingent on delivery of any future functionality or features. 21. Definitions “ Acceptable Use Policy ” means Atlassian’s acceptable use policy available at https://www.atlassian.com/legal/acceptable-use-policy . “ Advisory Services ” means advisory services as described in the Advisory Services Policy. “ Advisory Services Policy ” means Atlassian’s advisory services policy available at https://www.atlassian.com/legal/advisory-services-policy . “ Affiliate ” means an entity that, directly or indirectly, owns or controls, is owned or is controlled by or is under common ownership or control with a party, where “ownership” means the beneficial ownership of more than fifty percent (50%) of an entity’s voting equity securities or other equivalent voting interests and “control” means the power to direct the management or affairs of an entity. “ Agreement ” means this Atlassian Customer Agreement, as well as the Product-Specific Terms, the DPA and the Policies. “ Atlassian Apps ” means apps developed by Atlassian for use with Cloud Products or Software Products, as designated by Atlassian in the Atlassian Marketplace. “ Atlassian Marketplace ” means the online platform to purchase apps for Atlassian products currently branded the Atlassian Marketplace and accessible at https://marketplace.atlassian.com/. “ Cloud Products ” means Atlassian’s cloud products, including client software for its cloud products (“ Cloud Clients ”). “ Code of Conduct ” means the Atlassian Code of Business Conduct & Ethics, available at https://investors.atlassian.com/governance/governance-documents/default.aspx. “ Customer Data ” means any data, content or materials provided to Atlassian by or at the direction of Customer or its Users via the Cloud Products, including from Third-Party Products. “ Customer Materials ” means materials and other resources that Customer provides to Atlassian in connection with Support or Advisory Services. “ Documentation ” means Atlassian’s usage guidelines and standard technical documentation for the applicable Product, available at https://support.atlassian.com/ , unless otherwise specified in the Product-Specific Terms. “ DPA ” means the Atlassian data processing addendum available at https://www.atlassian.com/legal/data-processing-addendum. “ Laws ” means all applicable laws, regulations, conventions, decrees, decisions, orders, judgments, codes and requirements of any government authority (federal, state, local or international) having jurisdiction. “ Order ” means Atlassian’s ordering document, online sign-up or other ordering process that Atlassian enables specifying the Products, Support or Advisory Services to be provided under this Agreement, accepted by Atlassian in accordance with Section 9 (Ordering Process and Delivery). “ Policies ” means the Acceptable Use Policy, Advisory Services Policy, guidelines for Reporting Copyright and Trademark Violations, Privacy Policy, Security Measures, Service Level Agreement, Support Policy, Third-Party Code Policy and any additional Atlassian policies specified in Product-Specific Terms. “ Privacy Policy ” means Atlassian’s privacy policy available at https://www.atlassian.com/legal/privacy-policy . “ Products ” means the applicable Cloud Products or Software Products made available by Atlassian in connection with an Order. Products also include Atlassian Apps. “ Product-Specific Terms ” means product-specific terms that apply only to certain Products, available at https://www.atlassian.com/legal/product-terms . “ Reseller ” means a partner authorized by Atlassian to resell Atlassian’s Products, Support and Advisory Services to customers “ Scope of Use ” means Customer’s entitlements to the Products. Such entitlements may be based on: (a) number of licenses, copies or instances, (b) entity, division, business unit, website, or field of use, (c) number and type of Users, (d) number of queries, requests or other usage-based subscription units, or (e) other restrictions or billable units. “ Security Measures ” means Atlassian’s security practices available at https://www.atlassian.com/legal/security-measures . “ Service Level Agreement ” means the service level commitments, if any, for a Cloud Product as described at https://www.atlassian.com/legal/sla . “ Software Products ” means Atlassian’s installed software products and any generally-available bug fixes, updates and upgrades it provides to Customer, including through Support. “ Subscription Term ” means the term for Customer’s use of or access to the Products and related Support and Advisory Services as identified in an Order. “ Support ” means the level of support for the Products corresponding to Customer’s Scope of Use, as identified in the Support Policy. “ Support Policy ” means the Atlassian support offerings documentation available at https://confluence.atlassian.com/support/atlassian-support-offerings-193299636.html . “ Third-Party Code Policy ” means Atlassian’s third-party code policy available at https://www.atlassian.com/legal/third-party-code-policy . “ User ” means any individual that Customer authorizes to use the Products. Users may include: (i) Customer’s and its Affiliates’ employees, consultants, contractors and agents (ii) third parties with which Customer or its Affiliates transact business (iii) individuals invited by Customer’s users (iv) individuals under managed accounts, or (v) individuals interacting with a Product as Customer’s customer. Related cont | 2026-01-13T09:29:41 |
https://www.drupal.org/docs/contributed-modules/configuration-kits#content | Configuration Kits | Contributed module documentation | Drupal Wiki guide on Drupal.org Skip to main content Skip to search Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see ? Yes, please No, do not track me Drupal.org home Discover Drupal Drupal Core Drupal CMS Drupal AI Case Studies Drupal for Government Drupal for Higher Education Drupal for Nonprofit Drupal for eCommerce Drupal for FinTech Drupal for Healthcare Drupal for Enterprise Drupal for Retail Drupal for Travel & Tourism Build with Drupal Download Drupal Documentation Getting started Local Development Guide Developer Resources Drupal CMS User Guide Drupal User Guide API Modules Themes Distributions Issue queues Security Advisories Partners & Services Find a Drupal Certified Partner Become a Drupal Certified Partner Find a Hosting Provider Find a Migration Partner Find Training Drupal Steward Community About the Community How to Contribute DrupalCon Events Jobs / Careers News & Blogs Forum Slack Newsletters Drupal Swag Shop Support Drupal The Drupal Association Donate Become a Partner Become a Ripple Maker Become an Organization Member Drupal Swag Shop Get Started Try Drupal CMS Try Hosting Return to content Search form Search Log in Create account Documentation Search Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options. Migration Resource Center Drupal Extending Drupal Contributed modules Contributed module documentation Advertising sustains the DA. Ads are hidden for members. Join today Contributed module documentation Active Tags A11Y Paragraphs Tabs AI AI Interpolator AI Migration API Authentication API module APITools Accelerated Mobile Pages (AMP) Access NASA API Access Policy Accessibility Scanner Acquia Migrate: Accelerate Actions UI Activity Tracker module ActivityPub Add To Calendar Date Augmenter AddToAny Share Buttons Address Decoupled Address for Luxembourg Address for Rep. of Moldova Admin Menu Swap Adobe Launch Advanced CSS/JS Aggregation Advanced Email Validation Advanced File Destination - Ho to use Advanced Insert View Advanced Varnish Advanced Views RSS Feed Aggregator Akamai Album Photos Alexa Allow a content type only once (Only One) Altcha Anu LMS Apigee API Catalog Apigee Developer Portal Kickstart Apigee Edge Apigee Monetization Apple News Astrology Atoms AudioField Audit files Augmentor User Guide Authorization Auto Link Auto Node Translate Auto Taxonomy Term Translate AutoFloat Automatic Updates Avatar Kit Azure Drupal Sync BAT Guide BEE hotel Backstop Generator Backup and Migrate Bamboo Twig Barcodes Behat UI Better Exposed Filters Bibliography & Citation BigCommerce Block Class Block Form Alter Block List Override Block Style Plugins Blog Book Boost Bootstrap Layouts Bootstrap Paragraphs Bootstrap Quick Tabs Bootstrap Theme Toggler Block Bothive Chatbot Botman Boxout Braintree Cashier Breakgen Brightcove Video Connect Bundle override Burndown Business Rules Bynder CAS CDEK API CKEditor 4 LTS CKEditor 5 Premium Features CKEditor CKEditor Accessibility Auditor CKEditor CodeMirror CKEditor Entity Link CKEditor Font Size and Family CKEditor Google Search CKEditor Libraries Group CKEditor: N1ED plugin CMRF Core Documentation CSV Importer CSV to Config Cached moderation state Calendar View Canvas LTI Captcha Keypad Changed Fields API (8.x-3.x) Changed Fields API Chaos Tool Suite (ctools) Chart Suite Guide Charts Chatbot API Chatbot Framework Claro Cloud Cloudflare Stream Cloudinary Coder Collapsiblock Color Color Field Comment Notify Comment mover Commerce Commerce API Commerce Affirm Credit Payment Gateway Commerce Approve Commerce Authorize.Net Commerce Braintree Commerce Cart API Commerce Cart Flyout Commerce DIBS integration Commerce Easy Commerce Funds Commerce Google Tag Manager Commerce Ingenico Commerce Inventory Commerce Invoice Commerce Migrate Commerce NoFraud Commerce Order Document Commerce PVT Commerce Pagseguro Transparente Commerce PayPal Commerce Payment Extra Commerce Point of Sale (POS) Commerce PostFinance Checkout Commerce Postfinance Commerce Product Options Commerce Recurring Metered Commerce Rental Commerce Reporting Commerce Square Connect Commerce Time Slots Commerce Tpay Commerce TrustedShops Commerce Variation Add-on Commerce Webform Order Commerce iATS Commerce iDEAL Payment Gateway Component Schema Components Computed Field Computed Field Plugin Conditional Fields Config Override Inspector Config Pages Config Single Export Config Token Config partial export Configuration Kits Configuration Split Content Alerts Content Feedback Content Import Content Packager Content Planner Content Synchronization Content-Security-Policy ContentAccess Create fields programmatically Crossword CrowdSec CsvtoTable Cura Childcare Suite Cura Childcare Suite Currency Custom 4XX Pages Custom API Custom Field Custom Status Report Custom Tokens Custom Tokens and its snippets Custom breadcrumbs Customerror D8 Rules Essentials Dashboard Date Augmenter API Decoupled Blocks: Vue.js Decoupled Toolbox Decoupled Toolbox Decoupled quiz Default Content for D8 Delete Entity Translations Dempo Deploy Deploying Meilisearch to production Devel Devel Generate Commerce Developer Suite Developer portal Digital Signage Framework Disclosure Menu Disclosure Menu Display Suite Chained Fields Dominican Catalogus Module DraggableViews Drupal Chatbot Drupal Commerce Merchant Warrior Drupal Contribution Drupal Diversity & Inclusion Drupal Js Path Drupal LMS Drupal OAuth & OpenID Connect Login - OAuth2 Client SSO Login Drupal OAuth OIDC Login Drupal Remote Dashboard Drupal Slider Drupal Website Security – Complete Protection for Your Site Drupal WhatsApp Drupal YouTuber Drupal driver for SQL Server and SQL Azure DubBot ECA: Event - Condition - Action ECC EU Cookie Compliance EVA Easy Breadcrumb Easy News Editor Button Link Ek Jitsi Elasticsearch Connector Email Verification / SMS Verification / OTP Verification Encrypt Entitree Administration Guide Entity Access Password Entity Browser - Table Layout Entity Browser Entity Pager Entity Parser Entity Prepopulate Entity Print Entity Reference Facet Link Entity Reference Override Entity Reference Views Entity Reference Views Select Entity Registration Entity Search Autoindex Entity Share Entity Share WebSub Entity Update Entity Usage Entity Usage Addons Entity browser Environment indicator Epsilon Harmony Connector Ethereum Evaluate Webform Event Platform Events Logger Excel Importer Exerciser Usage Expire reset password link Extensions API External Authentication External Entities External Entities Database storage Extra Block Types (EBT) Extra Paragraph Types (EPT) Facebook Instant Articles Facet Bot Blocker Facets Facets Date Range Picker Factory Lollipop Feature Toggle Features Feeds Feeds Migrate Feeds Paragraphs Feeds extensible parsers Field Encrypt Field Gallery Field Group Field Inheritance Field description tooltip Field validation File Extractor Filebrowser FillPDF Firebase Authentication Guide Fivestar Flag Flag Lists Flashpoint Education Flexible Views Flickr Integration Suite Flow2 Fluent Flysystem Focal Point Focal Point FolderShare Guide Font Awesome Icons Footnotes Form mode manager FormAlter as Plugin FormAssembly Formatter Suite Guide Formdazzle! Forms steps FortyTwo Forum module Forward Freelinking Frontend Editing Frontify Assets FullCalendar Block Funding GA Push GIT Info Report GLightbox Gatsby Integration General Data Protection Regulation Geocluster D8/D9 Set-up Geofield Geolocation Field Get Linkedin Posts Ghost Inspector Integrator Ghost Inspector Integrator Gin Toolbar Custom Menu Ginger Robot Gardens Ginger Robot Suite Give GlobalDoc’s LangXpert Connect for Drupal Googalytics Google API PHP Client Google Analytics Google Analytics Counter Google Analytics Search API Autocomplete Google Authentication for Users Google Bard Google Calendar Import Google Programmable Search Engine Gophish Integration GovUK Notify GrapesJs Editor - Page builder GraphQL Grid Widget Group Group Content Moderation Group Flex Group Invite Group Media Group Subscription Group by Field Widget Grouper Usage Gutenberg Gutenberg Content Embed Gutenberg Starter Gutenberg Starter Gutenberg USWDS Guzzle REST Generator HAL HAX HTML Mail HTML Title HTTP Client Manager Hanging Conjunctions Filter HelloSign Hidden Tab Honeypot Hospital Price Transparency Hotkeys for Save How to Configure Drupal Sharepoint Integration How to test a module locally using DDEV (Webform Booking example) Human Presence Form Protection Hux IMCE File Manager IPMA Weather Iconify Icons If Then Else Iframe Media Embed Video Image Base64 Formatter Image Optimize Image Replace Imageshop Immoweb API Client In Other Words Inline Formatter Field Insert Instagram Block Integrating Frontify with Drupal: A Comprehensive Guide Intercept Islandora JSON Field Utils JSON:API Search API Janrain Connect Juicebox HTML5 Responsive Image Galleries Juicer - Social Media Feed Aggregator Key Keycloak OpenID Connect Klaro Consent Management Knowledge Konami Code LDAP Integration LDAP Integration with Active Directory and OpenLDAP - NTLM & Kerberos Login Language Negotiation Url Matrix Layout BG Layout Builder Additions Layout Builder Block Sanitizer Layout Builder Plus Layout Builder Restrictions Layout Builder Settings Report Layout Builder Styles Layout Builder Tabs Section Layout Components Layout Options Layout Paragraphs Lazy-load Leaflet Leaflet More Markers Libraries API LiftIgniter Lightgallery Lightning Accessibility Lightweight Directory Access Protocol (LDAP) Link attributes Link icon Linkback Linkit Lndr Localist Drupal Localization server Localized Configuration Loco Translate Loqate Ludwig Lunr search Maestro Maestro Activepieces Integration Mailchimp Maintenance Manage display Managing User Account Expiration with User Expire Module Mapbox Field Markdown Markdown Easy Markdown Exporter Marketing Cloud Mask Field Matomo Analytics Maxlength Media Contextual Crop Media Gallery Media Library Form Element Media PDF Thumbnail Media Video Micromodal Media: Acquia DAM Membership Menu Manipulator Menu Migration (Import & Export) Message Message Integration Message Thread Metatag Metatag Google Scholar Micro Site Microsoft Entra ID SSO Login Microsoft Entra sync Migrate Magician Migrate QA Migrate Source CSV Migrate Source GraphQL Migrate Source JCR Migration Tools Mime Mail Mix Modal Modifiers Moodle REST Mother May I Multilanguage Form Display Multiple Registration Multistep Form Framework Multiversion NASA Astronomy Picture of the Day NFT Name Field Nbox Node Type count Notify OAuth 1.0 OAuth Server - API Documentation OAuth Server - SSO Setup Guides OAuth2 & OpenID Connect OAuth2 Client OEmbed Lazyload OH Office 365 Connector One Time Password SMS Open ReadSpeaker OpenChurch OpenEDU OpenID Connect OpenID Connect Microsoft Azure Active Directory client OpenLayersD8 OpenQuestions Openlayers Oracle Driver Oracle Eloqua API Redux OwnTracks PCO - Planning Center Online API PHP filter PNX Gallery PNX Media Packages Packagist Pagedesigner Panopoly 2 for Drupal 8/9 Paragraph Group Paragraphs Paragraphs Bundles Paragraphs Bundles Import Paragraphs Collection Paragraphs Gridstack Paragraphs Role Visibility Parameter Message Paranoia Pathauto Patternkit Performance Budget Permalink Block Permanent Entities Permissions by Term Persistent Login PhotoSwipe Place Blocks Plotly.js Graphing Plupload Poll Popup field group Postoffice Potion Preprocessor Files Preprocessor Plugins Preview graph QL Private DNS Private Message Progressive Web App (PWA) Project Browser Protected Content Pusher API Quadstat Quick Edit Quick Node Clone Quickchat Quicklink RDF RELAXed Web Services RNG Rabbit MQ Radioactivity Range Slider Reactify theme & module Read time Recipes Cookbook Recombee Recurring Dates Field Recurring Events RegEx Field Validation Registration Confirm Email Address Registration codes Registration role Release Version Remote Stream Wrapper Responsive Background Image Responsive Class Field Responsive Image Formatter Tools (RIFT) Responsive Image Preload Responsive Tables Filter Responsive menu Rocket.Chat Integration Module Guide Role paywall Rules Rules API POST SAML Authentication SAML IDP 2.0 Single Sign On (SSO) - SAML Identity Provider SAML SP Single Sign On (SSO) - SAML Service Provider - by Miniorange SMS Framework SMS System SVG Image Field Salesforce ECA Integration Salesforce MFW Salesforce Suite Scheduled Transitions Scheduled Updates Scheduler Schema.org Blueprints Schema.org Metatag Search 404 Search API Search API AI Search API Autocomplete Search API Decoupled Search API Exclude Entity Search API Federated Solr Search API RediSearch Search API Sajari Search API Solr Search API Xunsearch Search API opensolr Search and Replace Scanner SearchStax Search API Select 2 Semantic Views Sender Service Worker Registration Setting up the Release Version module Shared Field Display Settings Sharerich Sherpa Webform ShrinkTheWeb Simple Content Notifications Simple Decoupled Preview Simple FB Connect Simple Instagram Feed Simple Node Importer Simple Page Manager Simple Popup Blocks Simple XML sitemap Simple multi step form Simplenews Single Content Sync Site Module Siteimprove Sitemap Sites Skilling Skins Skosmos Feeds Smart Content Overview Smart Date Smart Title Smart Trim Snippet manager Social API Social Auth Vipps Social Media Platforms Social Migration Social Post Facebook Socialfeed Socialfeed Songkick Sound Management Spectra Analytics Srijan theme Static Node Generator - How to use and Use cases Statistical Spam Filter Statistics Step by step guides to configure various 2FA / MFA / TFA methods Stop Administrator Login String Structure Sync Style Selector Style Switcher Styled Google Map Subgroup Summit Meeting List Superfish Drop-down Menus Swagger UI Field Formatter Swiper Formatter Switches Symfony Mailer Syncer Synonyms System Monitor TMGMT Capita TMGMT Plunet TacJS Tagify Targets Taxonomy Bulk Actions (TBA) Tealium iQ Tag Management Telephone International Widget Template Entities Template Whisperer TextRazor - Automatic text classification The Better Mega Menu Time's Up Token Token Filter Tom Select Tombstones Tone Toolshed Tooltip Tour Transaction Transform API Translation Management Tool Trending Topics Tweet Feed Twig Components Twig Render This Twig Tools Twig tweak Twitter API Block Twitter Tweets Typed Data API Enhancements UI Patterns UI Patterns Pattern Lab UI Styles URL Embed Ubercart Uikit Slideshow Ultimate table Field UniOne Unisender newsletter UpTime Widget Upload File History User CSV Import User Guide for Field Encrypted Searchable - FES User History User Session Management and Monitoring Using CAT tools for Drupal Varbase Editor Varnish purger Vertex AI Search Vertex AI Search Promoted Results Video Video Embed Field Video Toolbox View Transitions Views Add Button Views Bootstrap for Bootstrap 3 Views Bootstrap for Bootstrap 5 Views Bootstrap for Bootstrap4 Views Bulk Operations (VBO) Views Display Union Views Field View Views Local Tasks Views Mobile Views PDF Views RSS: Media (MRSS) Elements Views Reference Field Views Regex Functions Views Remote Data Views Send Views Slideshow Views TimelineJS Views filter content type Vipps Recurring Payments: Installation Visitors Visual Layout Suite Visual Website Optimizer VisualN Visualization Charts Vite Voting API Reaction Wallee Warden Wayfinding Web Page Archive Web Service Data Webform Webform Attachment Gated Download Webform Eloqua Webform GoogleSheets Webform Trello Webform Workflows Element Website Feedback When and why to use Link Param Propagator WissKI WordPress Migrate Wordcount Workbench Menu Access Workflow Workout Usage Workout Usage with Drush Workspace XML Sitemap XML-RPC Xero Sync YAML Content YAML To PHP Youtube Gallery Zoom API agGrid ePayco integration htmLawed HTML filter/purifier memoQ translation miniOrange User Provisioning reCaptcha v3 signageOS simplytest.me Token Configuration Kits Configuration kits are made to make life easier for site builders and module maintainers. This guide will help you use, extend, and create your own configuration kits. Create Your Own Configuration Kit How to export configuration and make your own reusable module Related Content Configuration Kits This project is meant as central registry for modules that act as a configuration kit, or include one or more as a submodule. Guide maintainers Drupal’s online documentation is © 2000-2026 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0 . PHP code is distributed under the GNU General Public License . Infrastructure management for Drupal.org provided by Need a Drupal 7 extended support partner? Consider Tag1. News items News Planet Drupal Social media Sign up for Drupal news Security advisories Jobs Our community Community Services , Training & Hosting Contributor guide Groups & meetups DrupalCon Code of conduct Documentation Documentation Drupal Guide Drupal User Guide Developer docs API.Drupal.org Drupal code base Download & Extend Drupal core Modules Themes Distributions Governance of community About Web accessibility Drupal Association About Drupal.org Terms of service Privacy policy Drupal is a registered trademark of Dries Buytaert . | 2026-01-13T09:29:41 |
https://dsf.berkeley.edu/papers/?C=M;O=A | Index of /papers Index of /papers Name Last modified Size Description Parent Directory - S2K-92-12.ps.Z 1993-06-30 10:06 51K icde94-arrays.ps.Z 1994-02-17 17:38 74K ERL-M90-36.ps.Z 1994-02-17 19:15 50K S2K-93-28.ps.Z 1994-02-17 19:15 69K sigmod91-multilevel.ps.Z 1994-02-17 19:15 52K ERL-M85-95.ps.Z 1994-02-17 19:15 80K ERL-M88-07.ps.Z 1994-02-17 19:15 65K ERL-M90-34.ps.Z 1994-02-17 19:15 88K S2K-93-30.ps.Z 1994-02-17 19:15 39K ERL-M85-67.ps.Z 1994-02-17 19:15 47K icde92-nobtree.ps.Z 1994-02-17 19:15 49K ERL-M87-13.ps.Z 1994-02-17 19:15 54K ERL-M85-59.ps.Z 1994-02-17 19:15 73K ERL-M86-40.ps.Z 1994-02-17 19:16 53K UCB-MS-mao.ps.Z 1994-02-17 19:16 98K ERL-M87-06.ps.Z 1994-02-17 19:16 60K ERL-M91-56.ps.Z 1994-02-17 19:16 51K ERL-M91-62.ps.Z 1994-03-18 19:43 63K sigirf91-index.ps.Z 1994-03-18 20:12 42K UCB-MS-zfong.ps.Z 1994-03-29 14:02 107K S2K-94-41.ps.Z 1994-03-31 12:14 151K ERL-M93-28.ps.Z 1994-04-12 12:11 381K ERL-M93-05.ps.Z 1994-05-21 04:02 424K ERL-M93-01.ps.Z 1994-05-21 04:13 384K UCB-MS-jtkohl.ps.Z 1994-05-21 04:15 99K ERL-M92-02.ps.Z 1994-05-21 04:17 71K icde94-mariposa.ps.Z 1994-05-21 04:25 71K S2K-94-58.ps.Z 1994-12-10 16:17 50K pdis94-mariposa.ps.Z 1995-05-09 15:30 54K ERL-M89-16.ps.Z 1995-06-03 22:47 38K ERL-M89-17.ps.Z 1995-06-03 22:57 34K sigmodr87-selec.ps.Z 1995-06-03 23:08 28K ERL-M87-15.ps.Z 1995-06-03 23:10 45K ERL-M86-59.ps.Z 1995-06-03 23:15 34K ERL-M88-19.ps.Z 1995-06-03 23:16 56K expertdb88-future.ps.Z 1995-06-03 23:18 31K tse88-rulemgr.ps.Z 1995-06-03 23:19 55K ERL-M89-82.ps.Z 1995-06-03 23:21 30K UCB-MS-plai.ps.Z 1995-06-03 23:29 61K UCB-MS-aoki.ps.Z 1995-06-03 23:32 62K ERL-M93-25.ps.Z 1995-06-03 23:35 41K S2K-93-31.ps.Z 1995-06-03 23:59 82K S2K-93-32.ps.Z 1995-06-03 23:59 77K S2K-94-49.ps.Z 1995-06-04 00:03 69K S2K-94-59.ps.Z 1995-06-04 00:38 54K S2K-94-56.ps.Z 1995-06-04 00:40 77K S2K-94-45.ps.Z 1995-06-04 00:45 82K S2K-91-04.ps.Z 1995-06-04 00:47 36K S2K-92-13.ps.Z 1995-06-04 00:48 95K S2K-92-16.ps.Z 1995-06-04 00:50 84K S2K-92-20.ps.Z 1995-06-04 00:50 93K S2K-93-29.ps.Z 1995-06-04 00:54 96K S2K-93-38.ps.Z 1995-06-04 00:56 90K ERL-M89-56.ps.Z 1995-06-04 01:24 54K ERL-M90-28.ps.Z 1995-06-04 01:51 55K ERL-M86-06.ps.Z 1995-06-04 02:00 43K S2K-94-50.ps.Z 1995-06-04 02:07 63K sigmodr90-ucb.ps.Z 1995-06-04 02:53 31K S2K-94-48.ps.Z 1995-06-04 03:03 85K compcon86-object.ps.Z 1995-06-04 03:04 30K vl94-zooming.msword.ps.Z 1995-06-04 03:06 61K vdb95-navcoord.msword.ps.Z 1995-06-04 03:12 222K sigmodr94-industry.ps.Z 1995-06-04 03:39 55K icde94-calendar.ps.Z 1995-06-04 03:41 149K LBL-TR-34229.ps.Z 1995-06-04 03:43 144K sigmod93-predmig.ps.Z 1995-06-04 04:11 68K UW-CS-TR-1252.ps.Z 1995-06-04 04:12 41K UCB-MS-sunita.tar.Z 1995-06-04 04:35 111K UCB-MS-paxson.tar 1995-06-04 04:38 170K UCB-MS-devine.tar 1995-06-04 04:43 150K UCB-MS-ginger.ps.Z 1995-06-04 04:48 11K comp95-chabot.ps.Z 1995-06-04 04:54 65K COPYRIGHT 1995-06-17 20:55 952 S2K-95-62.ps.Z 1995-08-26 22:18 106K S2K-95-63.ps.Z 1995-08-26 22:18 116K S2K-95-64.ps.Z 1995-08-26 22:18 316K S2K-95-65.ps.Z 1995-08-26 22:18 50K S2K-95-66.ps.Z 1995-08-26 22:18 86K vldb95-gist.ps.Z 1995-09-06 22:56 93K vldb95-rtree.ps.Z 1995-09-06 22:57 60K vldb95-tert.ps.Z 1995-10-09 18:59 83K S2K-93-25.ps.Z 1995-10-17 20:17 279K S2K-95-60.msword.ps.Z 1995-10-18 02:35 219K mss95-tert.ps.Z 1995-12-22 23:07 59K icde96-tioga2.ps.Z 1995-12-22 23:15 280K icde96-repl.ps.Z 1995-12-22 23:18 104K vis95-tioga2.ps.Z 1996-03-08 19:19 315K sigmod96-magic.ps.Z 1996-03-14 16:15 93K CSD-95-876.ps.Z 1996-03-16 19:05 77K www5-docs.ps.Z 1996-03-31 00:24 200K vldb96-cube.ps.Z 1996-09-21 21:02 147K vldb96-reord.ps.Z 1996-09-21 21:04 132K sigmod97-online.ps.Z 1997-02-14 10:55 224K pods97-index.ps.Z 1997-02-20 15:05 64K sigmod97-gist.ps.Z 1997-02-23 16:19 119K sigmod97-nowsort.ps.Z 1997-04-11 20:23 82K CSD-97-932.ps.Z 1997-04-11 20:26 255K dtj95-s2k.ps.Z 1997-04-11 20:28 262K CSD-96-908.ps.Z 1997-04-11 20:29 170K dtj95-repo.ps.Z 1997-04-11 20:29 455K icde97-dl.ps.Z 1997-04-11 20:37 215K vldbj96.ps.Z 1997-04-11 21:49 121K CSD-95-876.pdf 1997-04-12 00:27 196K CSD-96-908.pdf 1997-04-12 00:27 68K CSD-97-932.pdf 1997-04-12 00:27 212K ERL-M85-59.pdf 1997-04-12 00:27 88K ERL-M85-67.pdf 1997-04-12 00:27 54K ERL-M85-95.pdf 1997-04-12 00:27 97K ERL-M86-06.pdf 1997-04-12 00:27 56K ERL-M86-40.pdf 1997-04-12 00:27 69K ERL-M86-59.pdf 1997-04-12 00:27 40K ERL-M87-06.pdf 1997-04-12 00:27 69K ERL-M87-13.pdf 1997-04-12 00:27 70K ERL-M87-15.pdf 1997-04-12 00:27 54K ERL-M88-07.pdf 1997-04-12 00:27 73K ERL-M88-19.pdf 1997-04-12 00:27 65K ERL-M89-16.pdf 1997-04-12 00:27 45K ERL-M89-17.pdf 1997-04-12 00:27 34K ERL-M89-56.pdf 1997-04-12 00:27 71K ERL-M89-82.pdf 1997-04-12 00:27 32K ERL-M90-28.pdf 1997-04-12 00:27 74K ERL-M90-34.pdf 1997-04-12 00:27 113K ERL-M90-36.pdf 1997-04-12 00:27 61K ERL-M91-56.pdf 1997-04-12 00:27 60K ERL-M91-62.pdf 1997-04-12 00:27 80K ERL-M92-02.pdf 1997-04-12 00:27 92K ERL-M93-01.pdf 1997-04-12 00:27 651K ERL-M93-05.pdf 1997-04-12 00:27 811K ERL-M93-25.pdf 1997-04-12 00:27 50K ERL-M93-28.pdf 1997-04-12 00:27 618K S2K-91-04.pdf 1997-04-12 00:27 38K S2K-92-13.pdf 1997-04-12 00:27 170K S2K-92-16.pdf 1997-04-12 00:27 140K S2K-92-20.pdf 1997-04-12 00:27 217K S2K-93-25.pdf 1997-04-12 00:27 211K S2K-93-28.pdf 1997-04-12 00:27 78K S2K-93-29.pdf 1997-04-12 00:27 210K S2K-93-30.pdf 1997-04-12 00:27 44K S2K-93-31.pdf 1997-04-12 00:27 91K S2K-93-32.pdf 1997-04-12 00:27 202K S2K-93-38.pdf 1997-04-12 00:27 99K S2K-94-45.pdf 1997-04-12 00:27 207K S2K-94-48.pdf 1997-04-12 00:27 102K S2K-94-49.pdf 1997-04-12 00:27 84K S2K-94-50.pdf 1997-04-12 00:27 167K S2K-94-56.pdf 1997-04-12 00:27 194K S2K-94-58.pdf 1997-04-12 00:27 55K S2K-94-59.pdf 1997-04-12 00:27 154K S2K-95-60.pdf 1997-04-12 00:27 107K S2K-95-62.pdf 1997-04-12 00:27 284K S2K-95-63.pdf 1997-04-12 00:27 131K S2K-95-64.pdf 1997-04-12 00:27 587K S2K-95-65.pdf 1997-04-12 00:27 52K S2K-95-66.pdf 1997-04-12 00:27 91K UCB-MS-aoki.pdf 1997-04-12 00:27 93K UCB-MS-ginger.pdf 1997-04-12 00:27 4.2K UCB-MS-jtkohl.pdf 1997-04-12 00:27 194K UCB-MS-mao.pdf 1997-04-12 00:27 149K UCB-MS-plai.pdf 1997-04-12 00:27 86K UCB-MS-zfong.pdf 1997-04-12 00:27 155K UW-CS-TR-1252.pdf 1997-04-12 00:27 47K comp95-chabot.pdf 1997-04-12 00:27 88K compcon86-object.pdf 1997-04-12 00:27 34K dtj95-repo.pdf 1997-04-12 00:27 386K dtj95-s2k.pdf 1997-04-12 00:27 224K expertdb88-future.pdf 1997-04-12 00:27 34K icde92-nobtree.pdf 1997-04-12 00:27 56K icde94-arrays.pdf 1997-04-12 00:27 192K icde94-calendar.pdf 1997-04-12 00:27 260K icde94-mariposa.pdf 1997-04-12 00:27 73K icde96-repl.pdf 1997-04-12 00:27 270K icde96-tioga2.pdf 1997-04-12 00:27 487K icde97-dl.pdf 1997-04-12 00:27 179K mss95-tert.pdf 1997-04-12 00:27 143K pdis94-mariposa.pdf 1997-04-12 00:27 57K pods97-index.pdf 1997-04-12 00:27 185K sigirf91-index.pdf 1997-04-12 00:27 43K sigmod91-multilevel.pdf 1997-04-12 00:27 60K sigmod93-predmig.pdf 1997-04-12 00:27 135K sigmod96-magic.pdf 1997-04-12 00:27 213K sigmod97-gist.pdf 1997-04-12 00:27 140K sigmod97-nowsort.pdf 1997-04-12 00:27 182K sigmod97-online.pdf 1997-04-12 00:27 359K sigmodr87-selec.pdf 1997-04-12 00:27 32K sigmodr90-ucb.pdf 1997-04-12 00:27 32K sigmodr94-industry.pdf 1997-04-12 00:27 141K tse88-rulemgr.pdf 1997-04-12 00:27 68K vdb95-navcoord.pdf 1997-04-12 00:27 99K vis95-tioga2.pdf 1997-04-12 00:27 591K vl94-zooming.pdf 1997-04-12 00:27 22K vldb95-gist.pdf 1997-04-12 00:27 197K vldb95-rtree.pdf 1997-04-12 00:27 121K vldb95-tert.pdf 1997-04-12 00:27 217K vldb96-cube.pdf 1997-04-12 00:27 332K vldb96-reord.pdf 1997-04-12 00:27 260K vldbj96.pdf 1997-04-12 00:27 169K www5-docs.pdf 1997-04-12 00:27 146K UCB-PhD-sunita.ps.Z 1997-04-12 00:46 413K S2K-94-41.pdf 1997-04-12 00:58 68K UCB-PhD-olken.ps.Z 1997-05-04 23:01 448K UCB-PhD-olken.pdf 1997-05-04 23:08 1.0M UCB-PhD-sunita.pdf 1997-05-04 23:10 784K debull96-ordbms.ps.Z 1997-05-09 19:21 80K debull96-chabot.ps.Z 1997-05-09 19:22 911K debull96-chabot.pdf 1997-05-10 18:21 438K debull96-ordbms.pdf 1997-05-10 18:21 131K debull93-s2k.ps.Z 1997-05-10 18:21 79K debull93-s2k.pdf 1997-05-10 18:24 113K UW-CS-TR-1274.ps.Z 1997-05-12 17:03 157K S2K-92-12.pdf 1997-05-12 17:11 59K UW-CS-TR-1274.pdf 1997-05-12 17:15 379K CSD-97-950.pdf 1997-06-10 15:23 225K CSD-97-950.ps.Z 1997-06-25 18:42 115K S2K-91-01.ps.Z 1997-07-08 23:14 96K S2K-91-05.ps.Z 1997-07-08 23:14 41K S2K-93-23.ps.Z 1997-07-08 23:16 74K sigmod81-views.ps.Z 1997-07-22 22:52 24K CSD-83-144.ps.Z 1997-07-22 22:54 23K ERL-M83-74.ps.Z 1997-07-22 22:55 24K ERL-M84-87.ps.Z 1997-07-22 22:56 18K ERL-M84-58.ps.Z 1997-07-22 22:57 32K hpts85-nothing.ps.Z 1997-07-22 23:00 18K unpubl-perf.ps.Z 1997-08-04 16:46 79K ngits97-control.ps.Z 1997-08-24 21:49 63K S2K-95-60.ps.Z 1997-11-03 01:52 124K vdb95-navcoord.ps.Z 1997-11-03 01:53 328K vl94-zooming.ps.Z 1997-11-03 01:54 30K debull97-online.ps.Z 1997-11-05 04:51 233K tods98-xfunc.ps.Z 1997-11-05 16:59 208K tods98-xfunc.pdf 1997-11-05 16:59 448K Informix/ 1997-11-16 19:36 - CSD-97-968.pdf 1997-11-29 07:51 213K CSD-97-968.ps.Z 1997-11-29 07:51 410K icde98-search.ps.Z 1997-11-30 01:10 79K icde98-search.pdf 1997-11-30 01:12 130K LBL-TR-34229.pdf 1997-11-30 01:25 265K S2K-91-01.pdf 1997-11-30 01:27 115K ERL-M83-74.pdf 1997-11-30 01:28 27K ERL-M84-58.pdf 1997-11-30 01:28 37K ERL-M84-87.pdf 1997-11-30 01:28 21K FIND-NO-PDF 1997-11-30 01:30 212 CSD-83-144.pdf 1997-11-30 01:30 30K S2K-91-05.pdf 1997-11-30 01:30 43K S2K-93-23.pdf 1997-11-30 01:31 186K debull97-online.pdf 1997-11-30 01:31 251K hpts85-nothing.pdf 1997-11-30 01:31 19K ngits97-control.pdf 1997-11-30 01:31 134K sigmod81-views.pdf 1997-11-30 01:31 32K unpubl-perf.pdf 1997-11-30 01:32 80K debull97-reduction.ps.Z 1997-12-04 16:37 336K debull97-reduction.pdf 1997-12-04 16:42 590K hpca98-io.ps.Z 1997-12-04 16:50 109K hpca98-io.pdf 1997-12-04 16:51 217K www5-docs/ 1998-01-22 22:15 - avi98-density.pdf 1998-01-26 01:01 150K avi98-density.ps.Z 1998-01-26 01:01 244K chi98-zoom.ps.Z 1998-02-21 03:27 37K chi98-zoom.pdf 1998-02-21 03:27 22K vis93-tioga.ps.Z 1998-04-20 15:24 54K vldb93-tioga.ps.Z 1998-04-20 15:25 95K vldb93-tioga.pdf 1998-04-20 15:50 219K vis93-tioga.pdf 1998-04-20 15:50 150K UCB-PhD-jsidell.doc 1998-04-22 13:38 1.0M chiie98-info.ps.Z 1998-08-05 21:40 129K chiie98-info.pdf 1998-08-05 21:41 50K CSD-98-1004.pdf 1998-08-11 14:46 231K CSD-98-1004.ps.Z 1998-08-11 14:46 106K sigmod98-ds.ps.Z 1998-08-12 00:32 134K sigmod98-ds.pdf 1998-08-12 00:32 70K sigmod98-amdb.ps.Z 1998-08-12 00:38 12K sigmod98-control.msword.ps.Z 1998-08-12 00:43 141K sigmod98-control.pdf 1998-08-12 00:44 73K sigmod98-amdb.pdf 1998-08-12 00:45 22K sigmod98-control.ps.Z 1998-08-12 00:47 204K sigmod98-ds.msword.ps.Z 1998-08-12 00:48 250K sigmodr98-idisk.ps.Z 1998-08-25 00:36 113K sigmodr98-idisk.pdf 1998-08-25 00:37 110K uist98-cid.msword.ps.Z 1998-09-04 02:37 401K uist98-cid.pdf 1998-10-01 02:49 151K CSD-98-1013.pdf 1998-10-05 22:52 224K CSD-98-1013.ps.Z 1998-10-05 22:53 102K CSD-98-1012.pdf 1998-10-05 22:54 273K CSD-98-1012.ps.Z 1998-10-05 22:54 334K Asilomar_Final.doc 1998-10-26 17:05 61K Asilomar_Final.htm 1998-10-26 17:05 33K CSD-98-1021.ps.Z 1998-11-02 16:32 159K CSD-98-1021.pdf 1998-11-02 16:35 230K stonebraker.bib 1998-11-02 16:41 41K debull98-vti.ps.Z 1998-11-02 16:51 65K debull98-vti.pdf 1998-11-02 16:52 53K uist98-cid.ps.Z 1998-11-03 01:49 222K vl98-viqing.msword.ps.Z 1998-11-03 01:59 305K vl98-viqing.pdf 1998-11-03 02:00 110K vl98-viqing.ps.Z 1998-11-03 02:01 193K amdb-framework.ps.Z.old 1999-02-07 20:46 404K amdb-framework.pdf.old 1999-02-07 20:47 1.6M sigda75-geo.ps.Z 1999-02-09 16:48 4.3M sigda75-geo.pdf 1999-02-09 16:57 3.8M UCB-PhD-woodruff.pdf 1999-02-11 21:08 1.0M UCB-PhD-woodruff.ps.Z 1999-02-11 21:08 1.7M vldb99-gist.ps.gz 1999-06-08 09:18 87K vldb99-gist.pdf 1999-06-08 09:19 88K uidis99-amdb.ps.gz 1999-06-26 13:16 124K uidis99-amdb.pdf 1999-06-26 13:21 124K ERL-M86-85.pdf 1999-08-09 14:10 15M ERL-M518.pdf 1999-08-13 15:16 2.9M index.html.old 1999-08-14 16:36 84K visual99-blobworld.ps.gz 1999-08-16 18:57 135K iopads99-river.ps 1999-08-16 19:00 229K spdt98-nowsort.ps 1999-08-16 19:07 152K sigfidet72-index.pdf 1999-08-19 18:12 1.0M sigmod74-indep.pdf 1999-08-19 18:46 1.2M icod82-rules.pdf 1999-08-19 18:58 1.0M sigmod83-adt.pdf 1999-08-19 19:24 1.2M iwoodb86-proc.pdf 1999-08-19 19:28 1.1M kms85-trigger.pdf 1999-08-19 19:37 1.6M pacific75-cupid.pdf 1999-08-19 19:39 661K pacific75-eval.pdf 1999-08-19 19:43 702K pacific75-model.pdf 1999-08-19 19:48 1.3M pacific75-storage.pdf 1999-08-19 19:52 1.2M amdb-framework.pdf 1999-08-25 00:24 209K amdb-framework.ps.gz 1999-08-25 00:24 214K amdb.pdf 1999-10-18 16:26 233K amdb.ps.gz 1999-10-18 16:26 206K sigmod00-eddy.ps 2000-03-01 00:47 2.6M sigmod00-eddy.pdf 2000-03-01 01:02 709K ERL/ 2001-12-01 17:46 - sigmod02-partial.pdf 2002-03-12 13:32 423K icde02-fjords.pdf 2002-03-12 13:39 517K sigmodr01-javatele.pdf 2002-03-12 13:41 167K iptps02-dhtquery.pdf 2002-03-12 13:45 124K sigmod02-cacq.pdf 2002-03-13 03:50 483K icde02-decoupled.pdf 2002-03-13 03:55 126K jacm02-indexability.pdf 2002-10-15 20:26 177K cidr03-tcq.pdf 2003-01-09 17:46 310K iptps03-feasability.pdf 2003-02-10 01:05 69K ipsn03-beyondavg.pdf 2003-04-28 22:42 667K icde03-fluxlb.pdf 2003-04-28 22:53 167K iptps03-feasibility.ps 2003-04-28 22:58 103K sigmod03-acqp.pdf 2003-04-28 23:41 425K icde03-stems.pdf 2003-05-01 23:06 329K vldb03-pier.pdf 2003-06-15 23:47 168K iptps04-hybridsearch.pdf 2004-02-16 10:30 145K sigmod04-fluxft.pdf 2004-03-22 17:19 175K vldb04-piersearch.pdf 2004-06-11 18:14 293K vldb04-stairs.pdf 2004-06-12 20:32 222K vldb04-model.pdf 2004-06-14 11:33 453K vldb04-precision.pdf 2004-06-22 01:40 225K dmsn04-reduction.pdf 2004-08-06 18:09 6.3M hotnets04-routing.pdf 2004-11-02 15:00 159K hotnets04-wakeup.pdf 2004-11-03 10:17 129K tods05-tinydb.pdf 2004-11-07 19:16 2.2M cidr05-pier.pdf 2004-11-23 13:21 199K ewsn05-task.pdf 2004-12-23 14:40 1.6M sec21C-privatematch.pdf 2005-04-04 23:14 185K sigcomm05-placelab.pdf 2005-05-11 16:55 494K podc04-pht.pdf 2005-05-16 01:32 112K worlds04-infoplane.pdf 2005-05-16 01:32 56K sigcomm05-declarenet.pdf 2005-06-21 21:47 341K sosp05-p2.pdf 2005-08-20 22:05 658K ndss05-maelstrom.pdf 2005-11-21 10:25 371K osdi02-tag.pdf 2005-12-05 00:25 571K mobi02-madden.pdf 2005-12-05 00:27 217K ndss06-maelstrom.pdf 2006-02-25 20:45 373K hotnets2005-components.pdf 2006-02-25 20:51 212K spots06-sdlib.pdf 2006-02-28 22:12 826K sigmod06-declar.pdf 2006-03-30 00:59 332K data_triage_icde_2006.pdf 2006-04-11 20:48 726K ipsn06-tours.pdf 2006-07-04 20:09 175K vldb06-histogram.pdf 2006-07-04 20:12 893K icde06-triage.pdf 2006-07-04 20:38 726K icde06-ken.pdf 2006-07-04 20:45 1.9M vldb06-histogram.pdpdf 2006-07-05 21:01 893K icde07-proofsketch.pdf 2006-12-15 03:04 284K cidr07-phi.pdf 2006-12-15 03:09 139K infocom07-pca.pdf 2007-03-05 15:02 316K sigmod07-aggshare.pdf 2007-04-05 20:53 524K SSDBM07-tcqfastbit.pdf 2007-04-10 23:11 378K sensys07-dsn.pdf 2007-08-31 13:27 361K dune07.pdf 2007-11-10 21:08 261K fntdb07-architecture.pdf 2007-12-11 00:16 910K vldb08-evita.pdf 2008-06-23 11:06 351K vldb08-bayesstore.pdf 2008-07-12 13:00 766K ssdbm99.pdf 2008-08-07 14:12 90K ipsn09-rendezvousproxy.pdf 2009-02-26 17:13 1.7M ipsn09-sensorsummaries.pdf 2009-04-19 14:04 537K vldb09-madskills.pdf 2009-07-06 09:43 274K netdb09-idodeclare.pdf 2009-08-30 22:17 222K sigmod96-caching.pdf 2009-09-21 00:32 1.5M icde10-usher.pdf 2009-10-20 22:24 777K eurosys10-boom.pdf 2010-02-19 13:42 302K nsdi10-hop.pdf 2010-03-11 07:41 631K icde10-ie.pdf 2010-03-11 15:37 520K vldb10-qpie.pdf 2010-07-12 20:05 3.9M uist10-entry.pdf 2010-07-26 23:39 1.3M GlobeCom2008.pdf 2010-07-27 18:31 2.5M hotdep10-fts-dts.ps 2010-09-06 11:27 1.5M hotdep10-fts-dts.pdf 2010-09-06 11:27 257K sigrec10-declimperative.pdf 2010-11-21 17:38 198K cidr11-bloom.pdf 2010-12-15 08:23 261K cidr11-firstmile.pdf 2010-12-15 10:55 432K chi11-wrangler.pdf 2011-01-24 20:56 1.9M chi11-commentspace.pdf 2011-02-04 07:15 7.0M nsdi11-fate-destini.pdf 2011-03-08 22:12 516K sigmod11-hybridinference.pdf 2011-04-04 05:51 1.6M uist11-wrangler.pdf 2011-08-19 09:51 289K UCB-dedalus-semantics-tr.pdf 2011-11-29 10:32 659K dev12-shreddr.pdf 2012-02-15 16:22 1.4M datalog2011-dedalus.pdf 2012-03-05 00:03 255K dbtest12-bloom.pdf 2012-06-05 16:53 174K UCB-lattice-tr.pdf 2012-06-22 13:27 360K vldb12-pbs.pdf 2012-09-04 21:22 719K datalog2012-confluence.pdf 2012-09-04 23:41 134K socc12-blooml.pdf 2012-10-15 00:54 295K socc12-explicit.pdf 2012-10-15 01:00 132K uist12-dataplay.pdf 2012-10-15 02:11 785K vast12-interview.pdf 2012-10-23 11:44 229K vast12-XXXX/ 2012-10-23 11:48 - pods13-learning.pdf 2013-08-06 20:17 1.6M socc13-consistency.pdf 2013-09-16 23:23 138K sigmod13-bolton.pdf 2013-09-16 23:26 352K vldb14-hats.pdf 2013-12-26 12:25 285K icde14-blazes.pdf 2013-12-26 12:28 449K vldb14-edelweiss.pdf 2014-01-06 23:39 219K | 2026-01-13T09:29:41 |
https://aws.amazon.com/index.html | Cloud Computing Services - Amazon Web Services (AWS) Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account What's new Catch up on the most talked-about launches, updates, and success stories across AWS. Loading Loading Loading Loading Loading From startups to enterprises—AWS is how leaders power innovation Join the largest global community of innovators who trust AWS to accelerate transformation and redefine industries. View more stories 1 / 5 Software & Internet Adobe delivers marketing ROI using AWS View the story Artificial Intelligence WRITER is the end-to-end platform for enterprises to build, activate, and supervise AI agents View the story Media & Entertainment Condé Nast modernizes century-old publishing with new data and AI strategy on AWS View the story Advertising & Marketing Pinterest drives visual discovery for 600 million monthly users with AI on AWS View the story Aerospace & Satellite Blue Origin advances space exploration with agentic AI on AWS View the story I want to see new customer stories in healthcare Powering what’s next in every industry Discover how AWS helps organizations in every sector build, scale, and transform. Explore AWS for your industry Loading Loading Loading Loading Loading AWS Global Infrastructure The AWS Cloud spans 120 Availability Zones within 38 Geographic Regions, with announced plans for 10 more Availability Zones and 3 more AWS Regions in the Kingdom of Saudi Arabia, Chile, and the AWS European Sovereign Cloud. North America South America Europe Middle East Africa Asia Pacific Australia and New Zealand AWS Coverage Regions North America Geographic Regions 9 AWS GovCloud (US-East) AWS GovCloud (US-West) Canada (Central) Canada West (Calgary) Mexico (Central) US West (Northern California) US East (Northern Virginia) US East (Ohio) US West (Oregon) Available Coming soon Edge Locations 31 The AWS Cloud in North America has 31 Availability Zones within 9 Geographic Regions, with 31 Edge Network Locations and 3 Edge Cache Locations. Ashburn, VA Atlanta GA Boston, MA Chicago, IL Columbus, OH Dallas/Fort Worth, TX Denver, CO Hayward, CA Houston, TX Jacksonville, FL Kansas City, MO Los Angeles, CA Miami, FL Minneapolis, MN Montreal, QC Nashville, TN New York, NY Newark, NJ Palo Alto, CA Phoenix, AZ Philadelphia, PA Portland, OR Queretaro, MX Salt Lake City, UT San Jose, CA Seattle, WA South Bend, IN St. Louis, MO Tampa Bay, FL Toronto, ON Washington D.C. I want to try AWS for free Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:41 |
https://git-scm.com/book/gr/v2/%ce%a4%ce%b1-%ce%b8%ce%b5%ce%bc%ce%b5%ce%bb%ce%b9%cf%8e%ce%b4%ce%b7-%cf%83%cf%84%ce%bf%ce%b9%cf%87%ce%b5%ce%af%ce%b1-%cf%84%ce%bf%cf%85-Git-%ce%91%ce%bd%ce%b1%ce%b9%cf%81%ce%ad%cf%83%ce%b5%ce%b9%cf%82-undoing | Git - Αναιρέσεις (undoing) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Ξεκινώντας με το Git 1.1 Σχετικά με τον έλεγχο εκδόσεων 1.2 Σύντομο ιστορικό του Git 1.3 Τι είναι το Git; 1.4 Η γραμμή εντολών 1.5 Εγκατάσταση του Git 1.6 Ρύθμιση του Git για πρώτη φορά 1.7 Χρησιμοποιώντας τη βοήθεια 1.8 Ανακεφαλαίωση 2. Τα θεμελιώδη στοιχεία του Git 2.1 Απόκτηση αποθετηρίου Git 2.2 Καταγραφή αλλαγών στο αποθετήριο 2.3 Χρησιμοποιώντας το ιστορικό υποβολών 2.4 Αναιρέσεις (undoing) 2.5 Δουλεύοντας με απομακρυσμένα αποθετήρια 2.6 Ετικέτες 2.7 Συντομεύεσεις στο Git 2.8 Ανακεφαλαίωση 3. Διακλαδώσεις στο Git 3.1 Οι κλάδοι με λίγα λόγια 3.2 Βασικές έννοιες διακλαδώσεων και συγχωνεύσεων 3.3 Διαχείριση κλάδων 3.4 Ροές εργασίας με διακλαδώσεις 3.5 Απομακρυσμένοι κλάδοι 3.6 Αλλαγή βάσης (rebasing) 3.7 Ανακεφαλαίωση 4. Το Git στον διακομιστή 4.1 Τα πρωτόκολλα 4.2 Εγκατάσταση του Git σε διακομιστή 4.3 Δημιουργία δημόσιου κλειδιού SSH 4.4 Στήσιμο του διακομιστή 4.5 Δαίμονες του Git 4.6 Έξυπνο HTTP 4.7 GitWeb 4.8 GitLab 4.9 Επιλογές φιλοξενίας από τρίτους 4.10 Ανακεφαλαίωση 5. Κατανεμημένο Git 5.1 Κατανεμημένες ροές εργασίας 5.2 Συνεισφέροντας σε ένα έργο 5.3 Συντήρηση ενός έργου 5.4 Ανακεφαλαίωση 6. GitHub 6.1 Δημιουργία λογαριασμού και ρύθμισή του 6.2 Συνεισφορά σε έργο 6.3 Συντήρηση ενός έργου 6.4 Διαχείριση οργανισμώνν 6.5 Συγγραφή script στο GitHub 6.6 Ανακεφαλαίωση 7. Εργαλεία του Git 7.1 Επιλογή αναθεώρησης 7.2 Διαδραστική εργασία με το στάδιο καταχώρισης 7.3 Αποθέματα και Καθαρισμός 7.4 Υπογραφή της δουλειάς μας 7.5 Αναζήτηση 7.6 Η ιστορία ξαναγράφεται 7.7 Απομυθοποίηση της reset 7.8 Προχωρημένη Συγχώνευση 7.9 Rerere 7.10 Αποσφαλμάτωση με το Git 7.11 Υπομονάδες 7.12 Δεμάτιασμα δεδομένων 7.13 Replace 7.14 Αποθήκευση διαπιστευτηρίων 7.15 Ανακεφαλαίωση 8. Εξατομίκευση του Git 8.1 Διαμόρφωση Git 8.2 Γνωρίσματα του Git 8.3 Τα άγκιστρα του Git 8.4 Ένα παράδειγμα επιβολής πολιτικής από το Git 8.5 Ανακεφαλαίωση 9. Το Git και άλλα συστήματα 9.1 Το Git ως πελάτης 9.2 Μετανάστευση στο Git 9.3 Ανακεφαλαίωση 10. Εσωτερική λειτουργία του Git 10.1 Διοχετεύσεις και πορσελάνες 10.2 Αντικείμενα του Git 10.3 Αναφορές του Git 10.4 Πακετάρισμα αρχείων 10.5 Τα refspec 10.6 Πρωτόκολλα μεταφοράς 10.7 Διατήρηση και ανάκτηση δεδομένων 10.8 Μεταβλητές περιβάλλοντος 10.9 Ανακεφαλαίωση A1. Appendix A: Το Git σε άλλα περιβάλλοντα A1.1 Γραφικές διεπαφές A1.2 Το Git στο Visual Studio A1.3 Git στο Visual Studio Code A1.4 Git στο IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git στο Sublime Text A1.6 Το Git στο Bash A1.7 Το Git στο Zsh A1.8 Το Git στο Powershell A1.9 Ανακεφαλαίωση A2. Appendix B: Ενσωμάτωση του Git στις εφαρμογές μας A2.1 Γραμμή εντολών Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Εντολές Git A3.1 Ρύθμιση και διαμόρφωση A3.2 Λήψη και δημιουργία έργων A3.3 Βασική λήψη στιγμιοτύπων A3.4 Διακλάδωση και συγχώνευση A3.5 Κοινή χρήση και ενημέρωση έργων A3.6 Επιθεώρηση και σύγκριση A3.7 Αποσφαλμάτωση A3.8 Επιθέματα A3.9 Ηλεκτρονικό ταχυδρομείο A3.10 Εξωτερικά Συστήματα A3.11 Διοίκηση A3.12 Εντολές διοχέτευσης 2nd Edition 2.4 Τα θεμελιώδη στοιχεία του Git - Αναιρέσεις (undoing) Αναιρέσεις (undoing) Οποιαδήποτε στιγμή, μπορεί να θελήσουμε να αναιρέσουμε κάτι. Σε αυτό το κεφάλαιο, θα δούμε μερικά βασικά εργαλεία με τα οποία μπορούμε να αναιρέσουμε αλλαγές που έχουμε ήδη κάνει. Θα πρέπει να είμαστε προσεκτικοί γιατί δεν θα μπορούμε πάντα να αναιρέσουμε κάποιες από αυτές τις αναιρέσεις. Αυτή είναι μία από τις λίγες περιπτώσεις στο Git όπου μπορεί να χάσουμε μέρος της δουλειάς μας αν κάνουμε τις αναιρέσεις λανθασμένα. Μια συχνή αναίρεση που χρησιμοποιείται είναι η περίπτωση κατά την οποία υποβάλλουμε κάτι πολύ νωρίς και ενδεχομένως ξεχάσουμε να προσθέσουμε κάποια αρχεία ή κάνουμε κάποιο σφάλμα στο μήνυμα υποβολής. Αν θέλουμε να ξανακάνουμε τη συγκεκριμένη υποβολή, να προσθέσουμε τις αλλαγές που ξεχάσαμε, να τις βάλουμε στο στάδιο καταχώρησης και να τις ξαναϋποβάλλουμε, θα πρέπει να χρησιμοποιήσουμε την επιλογή --amend : $ git commit --amend Η εντολή αυτή παίρνει το στάδιο καταχώρησης και το χρησιμοποιεί για την υποβολή. Αν δεν έχουμε κάνει περαιτέρω αλλαγές από την τελευταία μας υποβολή (για παράδειγμα, αν εκτελέσουμε αυτή την εντολή αμέσως μετά από μια υποβολή), τότε το στιγμιότυπο του αποθετηρίου θα είναι ακριβώς το ίδιο και το μόνο που θα αλλάξαμε είναι το μήνυμα υποβολής. Όταν εκτελέσουμε την εντολή, θα εκκινήσει ο επεξεργαστής κειμένου, που θα περιέχει το μήνυμα της προηγούμενης υποβολής μας. Μπορούμε να επεξεργαστούμε το μήνυμα ως συνήθως, αλλά θα αντικαταστήσει την τελευταία μας υποβολή. Για παράδειγμα, αν κάνουμε μια υποβολή και μετά διαπιστώσουμε ότι ξεχάσαμε να καταχωρήσουμε τις αλλαγές ενός αρχείου που θέλουμε να συμπεριλάβουμε στην υποβολή αυτή, τότε μπορούμε να: $ git commit -m 'Initial commit' $ git add forgotten_file $ git commit --amend Καταλήγουμε με μια και μοναδική υποβολή· η δεύτερη υποβολή αντικαθιστά τα αποτελέσματα της πρώτης. Note Είναι σημαντικό να καταλάβετε ότι όταν τροποποιούμε (amend) την τελευταία σας υποβολή, στην πραγματικότητα δεν την τροποποιείτε αλλά την αντικαθιστείτε με μια εντελώς νέα, βελτιωμένη υποβολή που διώχνει την παλιά υποβολή και βάζει την νέα υποβολή στη θέση της. Ουσιαστικά, είναι σαν η προηγούμενη υποβολή να μη συνέβη ποτέ και δεν θα εμφανίζεται στο ιστορικό του αποθετηρίου. Η αξία της τροποποίησης των υποβολών είναι ότι κάνετε ελάσονες βελτιώσεις στην τελευταία σας υποβολή, χωρίς να μπουκώνετε το ιστορικό του αποθετηρίου σας με μηνύματα υποβολής της μορφής “Ωχ, ξέχασα να προσθέσω ένα αρχείο” ή “Να πάρει, διόρθωσα ένα τυπογραφικό στην προηγούμενη υποβολή”. Note Να τροποποιείτε (amend) υποβολές που υπάρχουν μόνο τοπικα και δεν τις έχετε ωθήσει πουθενά. Η τροποποίηση υποβολών που έχουν ήδη ωθηθεί και η ώθησή του κλάδου θα δημουργήσει προβλήματα στους συνεργάτες σας. Περισσότερες λεπτομέρειες για το τι συμβαίνει όταν κάνετε κάτι τέτοιο, και πώς να το διορθώσετε όταν είμαστε αυτός που την πατάει υπάρχουν στο Οι κίνδυνοι της αλλαγής βάσης . Αφαίρεση αρχείου από το στάδιο καταχώρησης (staging) Στις επόμενες δύο ενότητες θα δούμε πώς μπορούμε να διαχειριστούμε τις αλλαγές που έχουν γίνει στο στάδιο κατάχωρησης και στον κατάλογο εργασίας. Το καλό είναι ότι η εντολή που χρησιμοποιούμε για να προσδιορίσουμε την κατάσταση αυτών των δύο περιοχών, μας υπενθυμίζει και πώς να αναιρέσουμε τις αλλαγές σε αυτές τις περιοχές. Για παράδειγμα, έστω ότι έχουμε κάνει αλλαγές σε δύο αρχεία και θέλουμε να τα υποβάλλουμε ως ξεχωριστές αλλαγές, αλλά τα υποβάλαμε κατά λάθος και τα δύο με την εντολή git add * . Πώς μπορούμε να αναιρέσουμε την καταχώριση του ενός από τα δύο; Η εντολή git status μας υπενθυμίζει: $ git add * $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README modified: CONTRIBUTING.md Ακριβώς κάτω από το “Changes to be committed”, μας λέει να εκτελέσουμε git reset HEAD <file>… ώστε να αφαιρέσουμε την αλλαγή από το στάδιο καταχώρησης. Ας χρησιμοποιήσουμε λοιπόν αυτή τη συμβουλή για το αρχείο CONTRIBUTING.md : $ git reset HEAD CONTRIBUTING.md Unstaged changes after reset: M CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Η εντολή φαίνεται λίγο περίεργη, αλλά κάνει τη δουλειά. Το αρχείο CONTRIBUTING.md είναι τροποποιημένο, αλλά δεν βρίσκεται στο στάδιο καταχώρησης. Note Πράγματι, η εντολή git reset μπορεί να είναι επικίνδυνη, ιδιαίτερα αν την καλέσετε με τη σημαία --hard . Όμως στο συγκεκριμένο σενάριο, το αρχείο στον κατάλογο εργασίας σας δεν τροποποιείται, οπότε είναι σχετικά ασφαλές. Προς το παρόν, το μόνο που χρειάζεται να γνωρίζουμε για την εντολή git reset είναι η παραπάνω χρήση της. Θα μπούμε σε περισσότερες λεπτομέρειες για το τι κάνει η εντολή reset και πώς να γίνουμε καλύτεροι, ώστε να κάνουμε πραγματικά ενδιαφέροντα πράγματα στην ενότητα Απομυθοποίηση της reset . Αναίρεση τροποποίησης ενός αρχείου Τι μπορούμε να κάνουμε όμως αν διαπιστώσουμε ότι δεν θέλουμε να κρατήσουμε τις αλλαγές που κάναμε στο αρχείο CONTRIBUTING.md ; Πώς μπορούμε να το ξετροποποιήσουμε εύκολα — να το φέρουμε στη μορφή που είχε στην τελευταία του υποβολή (ή όπως ήταν όταν το κλωνοποιήσαμε ή όπως το φέραμε στον κατάλογο εργασίας μας); Ευτυχώς, η εντολή git status μας λέει πώς να το κάνουμε. Στο αποτέλεσμα του προηγούμενου παραδείγματος, η περιοχή με τα μη καταχωρημένα αρχεία είναι κάπως έτσι: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Η εντολή μας πληροφορεί ρητά πώς να απορρίψουμε τις αλλαγές που έχουμε κάνει. Ας κάνουμε ό,τι λέει: $ git checkout -- CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Μπορούμε να δούμε ότι οι αλλαγές έχουν επανέρθει στην προηγούμενη μορφή. Important Είναι σημαντικό να καταλάβουμε ότι η εντολή git checkout -- <file> είναι αρκετά επικίνδυνη. Όλες οι αλλαγές που έχουμε κάνει τοπικά σε αυτό το αρχείο έχουν πλέον χαθεί — το Git αντικατέστησε αυτό το αρχείο με την τελευταία έκδοσή του από το στάδιο καταχώρησης ή την υποβεβλημένη έκδοση. Να μην χρησιμοποιούμε αυτή την εντολή παρά μόνο αν είμαστε απολύτως σίγουροι ότι δεν θέλουμε να κρατήσουμε αυτές τις μη αποθηκευμένες τοπικές αλλαγές. Αν θέλουμε να κρατήσουμε τις αλλαγές που κάνουμε στο αρχείο, αλλά παρόλα αυτά χρειάζεται να το κάνουμε στην άκρη, θα πρέπει να εξετάσουμε τη φύλαξη των αλλαγών (stashing) και τη διακλάδωση (branching) στο κεφάλαιο Διακλαδώσεις στο Git , αυτοί συνήθως είναι καλύτεροι τρόποι. Θυμόμαστε, ότι έχει υποβληθεί (committed) στο Git μπορεί σχεδόν πάντα να ανακτηθεί. Μπορούμε να ανακτήσουμε ακόμα και υποβολές σε κλάδους που έχουν διαγραφεί ή υποβολές που επανεγγράφηκαν, με την εντολή git commit --amend (βλ. Ανάκτηση δεδομένων σχετικά με την ανάκτηση δεδομένων). Ωστόσο, αν κάτι δεν είναι υποβεβλημένο και το χάσουμε, είναι πολύ πιθανό να μην μπορέσουμε να το ανακτήσουμε. Αναίρεση αλλαγών με το git restore Στην έκδοση 2.23.0 του Git εισήχθη νεά εντολή: git restore . Βασικά είναι μια εναλλακτική της εντολής git reset που μόλις συζητήσαμε. Από την Git έκδοση 2.23.0 και μετά, το Git χρησιμοποιεί την git restore αντί της git reset για πολλές λειτουργίες αναίρεσης. Ας ξαναδούμε τα βήματά μας, και να αναιρέσουμε αλλαγές με την git restore αντί της git reset . Αφαίρεση αρχείου από το στάδιο καταχώρησης με χρήση της git restore Στις επόμενες δύο ενότητες θα δούμε πώς μπορούμε να διαχειριστούμε τις αλλαγές που έχουν γίνει στο στάδιο καταχώρησης και στον κατάλογο εργασίας. Το καλό είναι ότι η εντολή που χρησιμοποιούμε για να προσδιορίσουμε την κατάσταση αυτών των δύο περιοχών, μας υπενθυμίζει και πώς να αναιρέσουμε τις αλλαγές σε αυτές τις περιοχές. Για παράδειγμα, έστω ότι έχουμε κάνει αλλαγές σε δύο αρχεία και θέλουμε να τα υποβάλλουμε ως ξεχωριστές αλλαγές, αλλά τα υποβάλλαμε κατά λάθος και τα δύο με την εντολή git add * . Πώς μπορούμε να αναιρέσουμε την καταχώριση του ενός από τα δύο; Η εντολή git status μας υπενθυμίζει: $ git add * $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) modified: CONTRIBUTING.md renamed: README.md -> README Ακριβώς κάτω από το “Changes to be committed”, μας λέει να εκτελέσουμε git restore --staged <file>… ώστε να αφαιρέσουμε την αλλαγή από το στάδιο καταχώρησης. Ας χρησιμοποιήσουμε λοιπόν αυτή τη συμβουλή αυτή για το αρχείο CONTRIBUTING.md : $ git restore --staged CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Το αρχείο CONTRIBUTING.md είναι τροποποιημένο, αλλά δεν βρίσκεται στο στάδιο καταχώρησης. Αναίρεση τροποποίησης ενός αρχείου με την χρήση της git restore Τι μπορούμε να κάνουμε όμως αν διαπιστώσουμε ότι δεν θέλουμε να κρατήσουμε τις αλλαγές που κάναμε στο αρχείο CONTRIBUTING.md ; Πώς μπορούμε να το ξετροποποιήσουμε εύκολα — να το φέρουμε στη μορφή που είχε στην τελευταία του υποβολή (ή όπως ήταν όταν το κλωνοποιήσαμε ή όπως το φέραμε στον κατάλογο εργασίας μας); Ευτυχώς, η εντολή git status μας λέει πώς να το κάνουμε. Στο αποτέλεσμα του προηγούμενου παραδείγματος, η περιοχή με τα μη καταχωρημένα αρχεία είναι κάπως έτσι: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Η εντολή μας πληροφορεί ρητά πώς να απορρίψουμε τις αλλαγές που έχουμε κάνει. Ας κάνουμε ό,τι λέει: $ git restore CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README Important Είναι σημαντικό να καταλάβουμε ότι η εντολή git restore — <file> είναι αρκετά επικίνδυνη. Όλες οι αλλαγές που έχουμε κάνει τοπικά σε αυτό το αρχείο έχουν πλέον χαθεί — το Git αντικατέστησε αυτό το αρχείο με την τελευταία έκδοσή του από το στάδιο καταχώρησης ή την υποβεβλημένη έκδοση. Να μην χρησιμοποιούμε αυτή την εντολή παρά μόνο αν είμαστε απολύτως σίγουροι ότι δεν θέλουμε να κρατήσουμε αυτές τις μη αποθηκευμένες τοπικές αλλαγές. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://ftp.gnu.org/old-gnu/gnufsdb/?C=D;O=A | Index of /old-gnu/gnufsdb Index of /old-gnu/gnufsdb Name Last modified Size Description Parent Directory - gnufsdb-1.01.tar.gz 2000-06-26 22:15 79K Apache/2.4.52 (Trisquel_GNU/Linux) Server at ftp.gnu.org Port 443 | 2026-01-13T09:29:41 |
https://m.youtube.com/watch?v=qqao4QXLURY | How Boden uses Compass | Atlassian Presents: Unleash | Atlassian - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"visitorData":"Cgs4dXk2MlRaMlpVZyj-oJjLBjIKCgJLUhIEGgAgX2LfAgrcAjE1LllUPUZBWkFsdktHVlpBN0sya3VFRFYwQ2gxMkotQ01rdGlEbHJYVmZ5S3BySXFIb21DS2ZkbjA1SU9WMVprR29zazgyMk5qVzMzSGNPWkp1QVE1bVBqdjVHNndneHNaRlFpYkRKNkQ5Yk9lN0Q5TXdwcVdVMUw0TTNFMjZ1dGZDNHZPOGdVV0w5QWFockl1R3FBOGNJTnJzdXFjcnVvYy1sMVdYTy0weFZtT1RGSFdZSlIzWlVoX3NlNEdFYjh5RUt2TkpiQmNXQUpicWE2OC1xWVZPWHZrY1VsQ3QtWGZQX1JXNGRDcUlLNlgyd2NxMWM4QjdYbm0zVUc1Qng0R1JTSm4yckZmdlZWZG9ZeURZdnM0M1hwRnpOamlwTmtvZ1I2UUd1MGQ5WFJlbUNlYVhuR3l5Rl9aaUpPeWRJUnZ5STdvRmxfb1M1X2x5alZlcnZKc043UGJwZ4IB3wJ93Nr1tq7FX6S6wIzzDTYV1aF5jWLoMvCMzkoCcJfW4-Op1oFsqFy-2QCzUJeBCuX5kf-rSOsxGtZ_pv7eY8uvyLgIgmmSjb3aUMxFAcc8OmywzB2sBDf23ECHIdfreJSZ5PsW70Z8r3fSS0pw_wQud7Fo6Qn80E69Mng-IdDmyMPtbdGEG9KQ02EM8pyetKed3HczZ4xit21o5FmUBmtbNS-uoUhkizgDYmQVckTqJ9M9Wc93t0V4iyDighgn-Nl5b5I5XhLf3X4xwXQBVmQb4TV7QfdxY6Z3OkgJJQTpCUw1fYKBZkLIVQ0vWeNERq_sgavpCXUJB_yTZl6dtF-evD9CdFklFvkHWQeH-mgZXxHrZS4u5ZH0KhzZbzDO_JK8C25J5ty9vnRk51vbiW4zvC4jMtg696Yc9RgEwMv5jE6VSBWbNyDh4z8-eOSSFZlP5dHfIS1kr3z7TzOdqsM%3D","serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x89a514ff98f57e9e"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"Cgs4dXk2MlRaMlpVZyj-oJjLBjIKCgJLUhIEGgAgX2LfAgrcAjE1LllUPUZBWkFsdktHVlpBN0sya3VFRFYwQ2gxMkotQ01rdGlEbHJYVmZ5S3BySXFIb21DS2ZkbjA1SU9WMVprR29zazgyMk5qVzMzSGNPWkp1QVE1bVBqdjVHNndneHNaRlFpYkRKNkQ5Yk9lN0Q5TXdwcVdVMUw0TTNFMjZ1dGZDNHZPOGdVV0w5QWFockl1R3FBOGNJTnJzdXFjcnVvYy1sMVdYTy0weFZtT1RGSFdZSlIzWlVoX3NlNEdFYjh5RUt2TkpiQmNXQUpicWE2OC1xWVZPWHZrY1VsQ3QtWGZQX1JXNGRDcUlLNlgyd2NxMWM4QjdYbm0zVUc1Qng0R1JTSm4yckZmdlZWZG9ZeURZdnM0M1hwRnpOamlwTmtvZ1I2UUd1MGQ5WFJlbUNlYVhuR3l5Rl9aaUpPeWRJUnZ5STdvRmxfb1M1X2x5alZlcnZKc043UGJwZw%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRj3a-EKDkIrZY8WzvQzwbAQJnccjjEs51E7HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","metadataBadgeRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","avatarStackViewModel","dialogViewModel","dialogHeaderViewModel","collectionThumbnailViewModel","thumbnailHoverOverlayViewModel","badgeViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","endScreenPlaylistRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"Cgs4dXk2MlRaMlpVZyj-oJjLBjIKCgJLUhIEGgAgX2LfAgrcAjE1LllUPUZBWkFsdktHVlpBN0sya3VFRFYwQ2gxMkotQ01rdGlEbHJYVmZ5S3BySXFIb21DS2ZkbjA1SU9WMVprR29zazgyMk5qVzMzSGNPWkp1QVE1bVBqdjVHNndneHNaRlFpYkRKNkQ5Yk9lN0Q5TXdwcVdVMUw0TTNFMjZ1dGZDNHZPOGdVV0w5QWFockl1R3FBOGNJTnJzdXFjcnVvYy1sMVdYTy0weFZtT1RGSFdZSlIzWlVoX3NlNEdFYjh5RUt2TkpiQmNXQUpicWE2OC1xWVZPWHZrY1VsQ3QtWGZQX1JXNGRDcUlLNlgyd2NxMWM4QjdYbm0zVUc1Qng0R1JTSm4yckZmdlZWZG9ZeURZdnM0M1hwRnpOamlwTmtvZ1I2UUd1MGQ5WFJlbUNlYVhuR3l5Rl9aaUpPeWRJUnZ5STdvRmxfb1M1X2x5alZlcnZKc043UGJwZw%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwihnZ6JmoiSAxWdUXgAHduEKCYyDHJlbGF0ZWQtYXV0b0iWoq2ukJyq06oBmgEFCAMQ-B3KAQToxFRt","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=_R2nZa8grno\u0026start_radio=1\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"_R2nZa8grno","params":"EAEYAcABAdoBBAgBKgC4BQE%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwihnZ6JmoiSAxWdUXgAHduEKCYyDHJlbGF0ZWQtYXV0b0iWoq2ukJyq06oBmgEFCAMQ-B3KAQToxFRt","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=_R2nZa8grno\u0026start_radio=1\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"_R2nZa8grno","params":"EAEYAcABAdoBBAgBKgC4BQE%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwihnZ6JmoiSAxWdUXgAHduEKCYyDHJlbGF0ZWQtYXV0b0iWoq2ukJyq06oBmgEFCAMQ-B3KAQToxFRt","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=_R2nZa8grno\u0026start_radio=1\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"_R2nZa8grno","params":"EAEYAcABAdoBBAgBKgC4BQE%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"How Boden uses Compass | Atlassian Presents: Unleash | Atlassian"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 7,278회"},"shortViewCount":{"simpleText":"조회수 7.2천회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CIsCEMyrARgAIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC3FxYW80UVhMVVJZGmBFZ3R4Y1dGdk5GRllURlZTV1VBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDNGeFlXODBVVmhNVlZKWkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CIsCEMyrARgAIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}}],"trackingParams":"CIsCEMyrARgAIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"33","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJYCEKVBIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},{"innertubeCommand":{"clickTrackingParams":"CJYCEKVBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJcCEPqGBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJcCEPqGBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"qqao4QXLURY"},"likeParams":"Cg0KC3FxYW80UVhMVVJZIAAyDAj-oJjLBhD9ppzHAg%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CJcCEPqGBCITCKGdnomaiJIDFZ1ReAAd24QoJg=="}}}}}}}]}},"accessibilityText":"다른 사용자 33명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJYCEKVBIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"34","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJUCEKVBIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},{"innertubeCommand":{"clickTrackingParams":"CJUCEKVBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"qqao4QXLURY"},"removeLikeParams":"Cg0KC3FxYW80UVhMVVJZGAAqDAj-oJjLBhDjvp3HAg%3D%3D"}}}]}},"accessibilityText":"다른 사용자 33명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJUCEKVBIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CIsCEMyrARgAIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtxcWFvNFFYTFVSWSA-KAE%3D","likeStatusEntity":{"key":"EgtxcWFvNFFYTFVSWSA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJMCEKiPCSITCKGdnomaiJIDFZ1ReAAd24QoJg=="}},{"innertubeCommand":{"clickTrackingParams":"CJMCEKiPCSITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJQCEPmGBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJQCEPmGBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"qqao4QXLURY"},"dislikeParams":"Cg0KC3FxYW80UVhMVVJZEAAiDAj-oJjLBhCfgp_HAg%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CJQCEPmGBCITCKGdnomaiJIDFZ1ReAAd24QoJg=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJMCEKiPCSITCKGdnomaiJIDFZ1ReAAd24QoJg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJICEKiPCSITCKGdnomaiJIDFZ1ReAAd24QoJg=="}},{"innertubeCommand":{"clickTrackingParams":"CJICEKiPCSITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"qqao4QXLURY"},"removeLikeParams":"Cg0KC3FxYW80UVhMVVJZGAAqDAj-oJjLBhCdrp_HAg%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJICEKiPCSITCKGdnomaiJIDFZ1ReAAd24QoJg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CIsCEMyrARgAIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","isTogglingDisabled":true}},"dislikeEntityKey":"EgtxcWFvNFFYTFVSWSA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtxcWFvNFFYTFVSWSD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJACEOWWARgCIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},{"innertubeCommand":{"clickTrackingParams":"CJACEOWWARgCIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtxcWFvNFFYTFVSWaABAQ%3D%3D","commands":[{"clickTrackingParams":"CJACEOWWARgCIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CJECEI5iIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJACEOWWARgCIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CI4CEOuQCSITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CI8CEPuGBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dqqao4QXLURY\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CI8CEPuGBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=qqao4QXLURY","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"qqao4QXLURY","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=aaa6a8e105cb5116\u0026ip=1.208.108.242\u0026initcwndbps=3540000\u0026mt=1768296063\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CI8CEPuGBCITCKGdnomaiJIDFZ1ReAAd24QoJg=="}}}}}},"trackingParams":"CI4CEOuQCSITCKGdnomaiJIDFZ1ReAAd24QoJg=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CIwCEOuQCSITCKGdnomaiJIDFZ1ReAAd24QoJg=="}},{"innertubeCommand":{"clickTrackingParams":"CIwCEOuQCSITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CI0CEPuGBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dqqao4QXLURY\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CI0CEPuGBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=qqao4QXLURY","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"qqao4QXLURY","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=aaa6a8e105cb5116\u0026ip=1.208.108.242\u0026initcwndbps=3540000\u0026mt=1768296063\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CI0CEPuGBCITCKGdnomaiJIDFZ1ReAAd24QoJg=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CIwCEOuQCSITCKGdnomaiJIDFZ1ReAAd24QoJg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CIsCEMyrARgAIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","dateText":{"simpleText":"2023. 12. 20."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/hKhZC-qfqS8IE-lu5AxwDHqQt-mK6XyV-AWLom89Oycio7KouoOVm2yPiLdD7wVWNgxl4KS69g=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/hKhZC-qfqS8IE-lu5AxwDHqQt-mK6XyV-AWLom89Oycio7KouoOVm2yPiLdD7wVWNgxl4KS69g=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/hKhZC-qfqS8IE-lu5AxwDHqQt-mK6XyV-AWLom89Oycio7KouoOVm2yPiLdD7wVWNgxl4KS69g=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Atlassian","navigationEndpoint":{"clickTrackingParams":"CIoCEOE5IhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"url":"/@Atlassian","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCL1yMVRMh3vxitPiVaXfkoA","canonicalBaseUrl":"/@Atlassian"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CIoCEOE5IhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"url":"/@Atlassian","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCL1yMVRMh3vxitPiVaXfkoA","canonicalBaseUrl":"/@Atlassian"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 25.1만명"}},"simpleText":"구독자 25.1만명"},"trackingParams":"CIoCEOE5IhMIoZ2eiZqIkgMVnVF4AB3bhCgm","badges":[{"metadataBadgeRenderer":{"icon":{"iconType":"CHECK_CIRCLE_THICK"},"style":"BADGE_STYLE_TYPE_VERIFIED","tooltip":"인증됨","trackingParams":"CIoCEOE5IhMIoZ2eiZqIkgMVnVF4AB3bhCgm","accessibilityData":{"label":"인증됨"}}}]}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCL1yMVRMh3vxitPiVaXfkoA","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CPwBEJsrIhMIoZ2eiZqIkgMVnVF4AB3bhCgmKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Atlassian을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Atlassian을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Atlassian 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CIkCEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Atlassian 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Atlassian 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CIgCEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Atlassian 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CIECEJf5ASITCKGdnomaiJIDFZ1ReAAd24QoJg==","command":{"clickTrackingParams":"CIECEJf5ASITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CIECEJf5ASITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CIcCEOy1BBgDIhMIoZ2eiZqIkgMVnVF4AB3bhCgmMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQToxFRt","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ0wxeU1WUk1oM3Z4aXRQaVZhWGZrb0ESAggBGAAgBFITCgIIAxILcXFhbzRRWExVUlkYAA%3D%3D"}},"trackingParams":"CIcCEOy1BBgDIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CIYCEO21BBgEIhMIoZ2eiZqIkgMVnVF4AB3bhCgmMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQToxFRt","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ0wxeU1WUk1oM3Z4aXRQaVZhWGZrb0ESAggDGAAgBFITCgIIAxILcXFhbzRRWExVUlkYAA%3D%3D"}},"trackingParams":"CIYCEO21BBgEIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CIICENuLChgFIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIICENuLChgFIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CIMCEMY4IhMIoZ2eiZqIkgMVnVF4AB3bhCgm","dialogMessages":[{"runs":[{"text":"Atlassian"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CIUCEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgmMgV3YXRjaMoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCL1yMVRMh3vxitPiVaXfkoA"],"params":"CgIIAxILcXFhbzRRWExVUlkYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CIUCEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CIQCEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CIICENuLChgFIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CPwBEJsrIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CIACEP2GBCITCKGdnomaiJIDFZ1ReAAd24QoJjIJc3Vic2NyaWJlygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dqqao4QXLURY%26continue_action%3DQUFFLUhqbkYxUUpXeENtYjlHVHAtT2RzLXhLNkxVZGdsZ3xBQ3Jtc0ttSmZrOUJyY0N4ZnJ3cDBmX3JLbGhKYzEya0FzbER5QU0xSHZNYlhrbG9OaWpjWExqZEhMVk92VDlFcGozTDFZcFJkd2tDMDFaUlRHN0FlUDN3cFhTSDdiM3JzNE5JaTNBd2tac1RkNHJsWFE4QW9PdTFXV2VXLVdBWVVPZFR4b0wyYjhLdnNiVHREcXcyM0xIWHpVQmJkZGtSLXE3djNBdWE0Q1h5VXcyNlNseVpqMm5KODR5MUxZUk9icEc5SDlmdHBpVTE\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CIACEP2GBCITCKGdnomaiJIDFZ1ReAAd24QoJsoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=qqao4QXLURY","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"qqao4QXLURY","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=aaa6a8e105cb5116\u0026ip=1.208.108.242\u0026initcwndbps=3540000\u0026mt=1768296063\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbkYxUUpXeENtYjlHVHAtT2RzLXhLNkxVZGdsZ3xBQ3Jtc0ttSmZrOUJyY0N4ZnJ3cDBmX3JLbGhKYzEya0FzbER5QU0xSHZNYlhrbG9OaWpjWExqZEhMVk92VDlFcGozTDFZcFJkd2tDMDFaUlRHN0FlUDN3cFhTSDdiM3JzNE5JaTNBd2tac1RkNHJsWFE4QW9PdTFXV2VXLVdBWVVPZFR4b0wyYjhLdnNiVHREcXcyM0xIWHpVQmJkZGtSLXE3djNBdWE0Q1h5VXcyNlNseVpqMm5KODR5MUxZUk9icEc5SDlmdHBpVTE","idamTag":"66429"}},"trackingParams":"CIACEP2GBCITCKGdnomaiJIDFZ1ReAAd24QoJg=="}}}}}},"subscribedEntityKey":"EhhVQ0wxeU1WUk1oM3Z4aXRQaVZhWGZrb0EgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CPwBEJsrIhMIoZ2eiZqIkgMVnVF4AB3bhCgmKPgdMgV3YXRjaMoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCL1yMVRMh3vxitPiVaXfkoA"],"params":"EgIIAxgAIgtxcWFvNFFYTFVSWQ%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CPwBEJsrIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPwBEJsrIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CP0BEMY4IhMIoZ2eiZqIkgMVnVF4AB3bhCgm","dialogMessages":[{"runs":[{"text":"Atlassian"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CP8BEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgmKPgdMgV3YXRjaMoBBOjEVG0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCL1yMVRMh3vxitPiVaXfkoA"],"params":"CgIIAxILcXFhbzRRWExVUlkYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CP8BEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CP4BEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Hear from James Crowe, Head of Software Development at Boden, about how they use Compass to help their engineers work smarter and more efficiently.\n\nSUBSCRIBE to get the latest: / @atlassian \n\nLearn more about Compass: https://www.atlassian.com/software/co... \n\nConnect with Atlassian:\n\n / atlassian \n\n / atlassian \n\n / atlassian \n\n / atlassian ","commandRuns":[{"startIndex":178,"length":17,"onTap":{"innertubeCommand":{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"url":"/channel/UCL1yMVRMh3vxitPiVaXfkoA","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCL1yMVRMh3vxitPiVaXfkoA","canonicalBaseUrl":"/channel/UCL1yMVRMh3vxitPiVaXfkoA"}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"YouTube Channel Link: @Atlassian"}}},{"startIndex":226,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmSJaira6QnKrTqgHKAQToxFRt","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqblNHUm9DeXgwaUZiMXY3UFBtb3RNT0ItQ0hBZ3xBQ3Jtc0tuVklGQXY0eF9UbHZYakF6UDFqZlhPMVpzSlNFRHVSZE5Vc1dhR3UtRnBKUXl5ZHh6YjNOV2xZU2pQTUNJTkhjNVpSU0VSdVZoa3FLS0tsMl9RWU9QbXViN05vS21JalhBNTlZdmp5MnZVVS1rNXptTQ\u0026q=https%3A%2F%2Fwww.atlassian.com%2Fsoftware%2Fcompass\u0026v=qqao4QXLURY","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqblNHUm9DeXgwaUZiMXY3UFBtb3RNT0ItQ0hBZ3xBQ3Jtc0tuVklGQXY0eF9UbHZYakF6UDFqZlhPMVpzSlNFRHVSZE5Vc1dhR3UtRnBKUXl5ZHh6YjNOV2xZU2pQTUNJTkhjNVpSU0VSdVZoa3FLS0tsMl9RWU9QbXViN05vS21JalhBNTlZdmp5MnZVVS1rNXptTQ\u0026q=https%3A%2F%2Fwww.atlassian.com%2Fsoftware%2Fcompass\u0026v=qqao4QXLURY","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":298,"length":15,"onTap":{"innertubeCommand":{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmSJaira6QnKrTqgHKAQToxFRt","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbTdaWHFOT2Q4czJCY2dfYlZoME9pdFN0aWtEd3xBQ3Jtc0trS3dNSGVqWWFWS3B6M3VkY1NUdHR4VHYyb2piMGhhN19USDVma1locnd3bV9udDlTY0laVTBDa2xYRXdzX3ZfWU41eUNOclJUUl9yUzNUSU9tRXNfQmREMHVkSU0yUHY3aEV2QTlQRHhVdUZtV3ppaw\u0026q=https%3A%2F%2Ftwitter.com%2FAtlassian\u0026v=qqao4QXLURY","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbTdaWHFOT2Q4czJCY2dfYlZoME9pdFN0aWtEd3xBQ3Jtc0trS3dNSGVqWWFWS3B6M3VkY1NUdHR4VHYyb2piMGhhN19USDVma1locnd3bV9udDlTY0laVTBDa2xYRXdzX3ZfWU41eUNOclJUUl9yUzNUSU9tRXNfQmREMHVkSU0yUHY3aEV2QTlQRHhVdUZtV3ppaw\u0026q=https%3A%2F%2Ftwitter.com%2FAtlassian\u0026v=qqao4QXLURY","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: Atlassian"}}},{"startIndex":319,"length":15,"onTap":{"innertubeCommand":{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmSJaira6QnKrTqgHKAQToxFRt","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbDdwSHJiQ3hrUGRRRkx3T2RJb1JKd1Jqb3ZsUXxBQ3Jtc0tsWk9DZXZyR0pUbGRfUU5DdGc1NUpqOTcxcXVFa1ZndE95WUFNRHJJNklFWGN0clRIOVNxdVJMSFR6cWtfTUJSSjNkVjUxX3A0Vkh4Um0wSkMzTjdEYmJ2NmxFUzBzdGdGWFlKcDJ1OGRLa2Utbkhjdw\u0026q=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fatlassian\u0026v=qqao4QXLURY","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbDdwSHJiQ3hrUGRRRkx3T2RJb1JKd1Jqb3ZsUXxBQ3Jtc0tsWk9DZXZyR0pUbGRfUU5DdGc1NUpqOTcxcXVFa1ZndE95WUFNRHJJNklFWGN0clRIOVNxdVJMSFR6cWtfTUJSSjNkVjUxX3A0Vkh4Um0wSkMzTjdEYmJ2NmxFUzBzdGdGWFlKcDJ1OGRLa2Utbkhjdw\u0026q=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fatlassian\u0026v=qqao4QXLURY","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"LinkedIn Channel Link: atlassian"}}},{"startIndex":341,"length":15,"onTap":{"innertubeCommand":{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmSJaira6QnKrTqgHKAQToxFRt","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbUl6SU05U1EyMzh1VG1pU0pKaGxHbTJXdzZLZ3xBQ3Jtc0tuRHQ4bmF2YUsxdllFakdYU1VLeHNPZGltaHBGNzI0Qy1NT0ZnanFxSlpjc1RtZmNEdVNvRUNGTG5IbkVJVmpObVh2YnZrZXowMjhoWHEycVV0ajZhMGYwQm4zSUVIMHhGX0FxZUZ3TEstY29DNTRRTQ\u0026q=https%3A%2F%2Fwww.facebook.com%2FAtlassian%2F\u0026v=qqao4QXLURY","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbUl6SU05U1EyMzh1VG1pU0pKaGxHbTJXdzZLZ3xBQ3Jtc0tuRHQ4bmF2YUsxdllFakdYU1VLeHNPZGltaHBGNzI0Qy1NT0ZnanFxSlpjc1RtZmNEdVNvRUNGTG5IbkVJVmpObVh2YnZrZXowMjhoWHEycVV0ajZhMGYwQm4zSUVIMHhGX0FxZUZ3TEstY29DNTRRTQ\u0026q=https%3A%2F%2Fwww.facebook.com%2FAtlassian%2F\u0026v=qqao4QXLURY","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Facebook Channel Link: Atlassian"}}},{"startIndex":363,"length":15,"onTap":{"innertubeCommand":{"clickTrackingParams":"CPsBEM2rARgBIhMIoZ2eiZqIkgMVnVF4AB3bhCgmSJaira6QnKrTqgHKAQToxFRt","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbGhyMWR1NmJkM2NVZGRrSjR0UU5GdHkwalBGUXxBQ3Jtc0ttVmJsS2hkb056bE9yS0IyWVJYNTdGTTB2RnVFckFxcnhvWnhSRGI4ZHBxYmxMX1hQMUZQQU1GUUxrYWJmNnJlRmVUd2UwbGYtTTEwYXhWbkcxSWVWTWVTT2xCVkxfdU45QThHYTZSMUl1R2F0Sm1nWQ\u0026q=https%3A%2F%2Fwww.instagram.com%2Fatlassian\u0026v=qqao4QXLURY","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbGhyMWR1NmJkM2NVZGRrSjR0UU5GdHkwalBGUXxBQ3Jtc0ttVmJsS2hkb056bE9yS0IyWVJYNTdGTTB2RnVFckFxcnhvWnhSRGI4ZHBxYmxMX1hQMUZQQU1GUUxrYWJmNnJlRmVUd2UwbGYtTTEwYXhWbkcxSWVWTWVTT2xCVkxfdU45QThHYTZSMUl1R2F0Sm1nWQ\u0026q=https%3A%2F%2Fwww.instagram.com%2Fatlassian\u0026v=qqao4QXLURY","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Instagram Channel Link: atlassian"}}}],"styleRuns":[{"startIndex":0,"length":178,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":178,"length":17,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}}},{"startIndex":195,"length":31,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":226,"length":40,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":266,"length":32,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":298,"length":15,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}}},{"startIndex":313,"length":6,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":319,"length":15,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}}},{"startIndex":334,"length":7,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":341,"length":15,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}}},{"startIndex":356,"length":7,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":363,"length":15,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}}}],"attachmentRuns":[{"startIndex":180,"length":0,"element":{"type":{"imageType":{"image":{"sources":[{"url":"https://www.gstatic.com/youtube/img/watch/yt_favicon_ringo2.png"}]}}},"properties":{"layoutProperties":{"height":{"value":10,"unit":"DIMENSION_UNIT_POINT"},"width":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"margin":{"top":{"value":0.5,"unit":"DIMENSION_UNIT_POINT"}}}}},"alignment":"ALIGNMENT_VERTICAL_CENTER"},{"startIndex":299,"length":0,"element":{"type":{"imageType":{"image":{"sources":[{"url":"https://www.gstatic.com/youtube/img/watch/social_media/twitter_1x_v2.png"}]}}},"properties":{"layoutProperties":{"height":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"width":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"margin":{"top":{"value":0.5,"unit":"DIMENSION_UNIT_POINT"}}}}},"alignment":"ALIGNMENT_VERTICAL_CENTER"},{"startIndex":320,"length":0,"element":{"type":{"imageType":{"image":{"sources":[{"url":"https://www.gstatic.com/youtube/img/watch/social_media/linkedin_1x.png"}]}}},"properties":{"layoutProperties":{"height":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"width":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"margin":{"top":{"value":0.5,"unit":"DIMENSION_UNIT_POINT"}}}}},"alignment":"ALIGNMENT_VERTICAL_CENTER"},{"startIndex":342,"length":0,"element":{"type":{"imageType":{"image":{"sources":[{"url":"https://www.gstatic.com/youtube/img/watch/social_media/facebook_1x.png"}]}}},"properties":{"layoutProperties":{"height":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"width":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"margin":{"top":{"value":0.5,"unit":"DIMENSION_UNIT_POINT"}}}}},"alignment":"ALIGNMENT_VERTICAL_CENTER"},{"startIndex":364,"length":0,"element":{"type":{"imageType":{"image":{"sources":[{"url":"https://www.gstatic.com/youtube/img/watch/social_media/instagram_1x.png"}]}}},"properties":{"layoutProperties":{"height":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"width":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"margin":{"top":{"value":0.5,"unit":"DIMENSION_UNIT_POINT"}}}}},"alignment":"ALIGNMENT_VERTICAL_CENTER"}],"decorationRuns":[{"textDecorator":{"highlightTextDecorator":{"startIndex":178,"length":17,"backgroundCornerRadius":8,"bottomPadding":1,"highlightTextDecoratorExtensions":{"highlightTextDecoratorColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":452984831},{"key":"USER_INTERFACE_THEME_LIGHT","value":218103808}]}}}}},{"textDecorator":{"highlightTextDecorator":{"startIndex":298,"length":15,"backgroundCornerRadius":8,"bottomPadding":1,"highlightTextDecoratorExtensions":{"highlightTextDecoratorColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":452984831},{"key":"USER_INTERFACE_THEME_LIGHT","value":218103808}]}}}}},{"textDecorator":{"highlightTextDecorator":{"startIndex":319,"length":15,"backgroundCornerRadius":8,"bottomPadding":1,"highlightTextDecoratorExtensions":{"highlightTextDecoratorColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":452984831},{"key":"USER_INTERFACE_THEME_LIGHT","value":218103808}]}}}}},{"textDecorator":{"highlightTextDecorator":{"startIndex":341,"length":15,"backgroundCornerRadius":8,"bottomPadding":1,"highlightTextDecoratorExtensions":{"highlightTextDecoratorColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":452984831},{"key":"USER_INTERFACE_THEME_LIGHT","value":218103808}]}}}}},{"textDecorator":{"highlightTextDecorator":{"startIndex":363,"length":15,"backgroundCornerRadius":8,"bottomPadding":1,"highlightTextDecoratorExtensions":{"highlightTextDecoratorColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":452984831},{"key":"USER_INTERFACE_THEME_LIGHT","value":218103808}]}}}}}]},"headerRuns":[{"startIndex":0,"length":178,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":178,"length":17,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":195,"length":31,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":226,"length":40,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":266,"length":32,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":298,"length":15,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":313,"length":6,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":319,"length":15,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":334,"length":7,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":341,"length":15,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":356,"length":7,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":363,"length":15,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CPoBELsvGAMiEwihnZ6JmoiSAxWdUXgAHduEKCbKAQToxFRt","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SC3FxYW80UVhMVVJZGAYyJSIRIgtxcWFvNFFYTFVSWTAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CPoBELsvGAMiEwihnZ6JmoiSAxWdUXgAHduEKCY=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CPkBELovIhMIoZ2eiZqIkgMVnVF4AB3bhCgm"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/oqZttIhOV5U/hqdefault.jpg?sqp=-oaymwE8CKgBEF5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARgTIEQofzAP\u0026rs=AOn4CLDnTT7w9SJMyUxnixVPJvzgbNQ6sA","width":168,"height":94},{"url":"https://i.ytimg.com/vi/oqZttIhOV5U/hqdefault.jpg?sqp=-oaymwE9CNACELwBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYEyBEKH8wDw==\u0026rs=AOn4CLDhjdxzP5XSBn4O82ZTCqo8hS7EEg","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"21:36","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"oqZttIhOV5U","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"21분 36초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CPgBEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"oqZttIhOV5U","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPgBEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgm","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CPcBEPBbIhMIoZ2eiZqIkgMVnVF4AB3bhCgmygEE6MRUbQ==","command | 2026-01-13T09:29:41 |
https://ftp.gnu.org/old-gnu/gnotary/?C=M;O=A | Index of /old-gnu/gnotary Index of /old-gnu/gnotary Name Last modified Size Description Parent Directory - client/ 2005-08-17 17:58 - Apache/2.4.52 (Trisquel_GNU/Linux) Server at ftp.gnu.org Port 443 | 2026-01-13T09:29:41 |
https://hubbedin.com/find-hiring-manager-landing | Find Hiring Manager Stand Out and Get Hired Increase your chances to stand out from the crowd of jobseekers using our AI-powered Jobseeker Assistant to connect directly with hiring managers. Connect with The Right People We'll help you get their email and Linkedin to get hired faster by providing you with direct access to the hiring managers at the companies you're interested in. Connect Now Personalized AI Message Craft a personalized message effortlessly using our platform. We analyze your resume, the job details, and the recipient to increase your chances of getting hired. Connect Now Stay Informed Using our resume builder’s tracker feature, you can see when it was first opened, number of downloads, and how many people have opened your resume. Connect Now Take your job search to the next level with our AI tools View Plans Our Careers Contact Us AI for Schools Talents Story Tech Jobs Marketing Jobs Browse Companies Consult a Recruiter Employer Free Job Posting Video Interview Online Assessment Headhunters Employer Branding Resources Podcast Journals Contact Us Got any question or suggestion for HubbedIn? Reach out to hello@hubbedin.com Socials © Copyright Hubbedin 2026 — All rights reserved. Personal Data Protection Policy Data Protection Notice About Us FAQ Privacy Policy Terms of Service Talents Story Tech Jobs Marketing Jobs Browse Companies Consult a Recruiter Employer Free Job Posting Video Interview Online Assessment Headhunters Employer Hubbedin Personal Data Protection Policy Data Protection Notice About Us FAQ Contact Us Our Careers AI for Schools Privacy Policy © Copyright Hubbedin 2026 — All rights reserved. | 2026-01-13T09:29:41 |
https://www.velir.com/ | Velir: A Data-Driven Digital Marketing Agency | Velir Skip to main content Who We Are Who We Are About Us Learn how we've evolved to drive smarter customer experiences. DEI Commitment We are committed to creating equal opportunities to learn, contribute, and succeed. Careers Explore opportunities to join our amazing team. What We Do What We Do We harness the superpower of data intelligence and marketing expertise to craft impactful digital experiences. Our Services Experience Design Platform Engineering Digital Marketing Data & AI Strategy Analytics & Insights Managed Services Our Partners Acquia Adobe Coveo Optimizely Sitecore Our Solutions Our Work Our Work Case Studies Explore our work to see how we bring bold digital ideas to life. Industries Discover how our deep expertise drives results across diverse sectors. Laying a Foundation for Suncoast’s Growth with XM Cloud Latest Ideas Data Studio Contact Close Search Submit Search Menu Close Who We Are Who We Are About Us Learn how we've evolved to drive smarter customer experiences. DEI Commitment We are committed to creating equal opportunities to learn, contribute, and succeed. Careers Explore opportunities to join our amazing team. What We Do What We Do We harness the superpower of data intelligence and marketing expertise to craft impactful digital experiences. Our Services Experience Design Platform Engineering Digital Marketing Data & AI Strategy Analytics & Insights Managed Services Our Partners Acquia Adobe Coveo Optimizely Sitecore Our Solutions Our Work Our Work Case Studies Explore our work to see how we bring bold digital ideas to life. Industries Discover how our deep expertise drives results across diverse sectors. Laying a Foundation for Suncoast’s Growth with XM Cloud Latest Ideas Data Studio Contact Search Submit Search Start of Main Content Digital Transformation Never Stops. Neither Do We. Digital evolves at lightning speed, and yesterday’s solutions won’t solve today’s challenges. That’s why Velir + Brooklyn Data go beyond building websites. We fuse strategy, creativity, and data to help organizations keep pace with change and lead it. By uniting Velir’s digital marketing and CX expertise with Brooklyn Data’s data and analytics expertise, we equip brands to adapt faster, engage deeper, and thrive in an environment where transformation isn’t optional - it’s constant. If you’re ready to shape what’s next, we’re ready to build it with you. Contact us Use Data to Take Your Digital Experiences to the Next Level Our teams can guide your organization in leveraging data intelligently to optimize your digital strategies and deliver tailored digital experiences that maximize audience engagement. Explore our services Digital Marketing Our digital marketing strategies ensure you reach, engage, and convert your target audience where they spend most of their time while driving brand visibility, growth, and business outcomes. About this service Digital Experience Our digital experience team helps you seize every moment in your audiences' journeys by anticipating their needs and delivering experiences that efficiently meet them. About this service Data Strategy Brooklyn Data, Velir's Data Studio, helps you get the most value from your organization's data with comprehensive strategies that revolutionize how you collect, manage, and analyze data. About this service Digital Marketing Our digital marketing strategies ensure you reach, engage, and convert your target audience where they spend most of their time while driving brand visibility, growth, and business outcomes. About this service Digital Experience Our digital experience team helps you seize every moment in your audiences' journeys by anticipating their needs and delivering experiences that efficiently meet them. About this service Data Strategy Brooklyn Data, Velir's Data Studio, helps you get the most value from your organization's data with comprehensive strategies that revolutionize how you collect, manage, and analyze data. About this service Harness the power of your data to gain insights and optimize your digital efforts Brooklyn Data, Velir's Data Studio, provides unparalleled data engineering and analytics consulting by collaborating with your team to develop the right data strategy and implement scalable cloud-data infrastructures. Let us help you become a data-enabled organization to deliver insights that inform decision-making and personalize your marketing. Learn about Brooklyn Data We are proud of the company we keep. Any digital agency can do project work, but not every agency can be a strategic partner to their clients. At Velir, we are proud to partner with some of the best organizations across industries and help them achieve their goals. See our case studies Our latest ideas Insights on digital trends and opportunities. Read our blog Ready to kick off your next project? Let's chat! Contact us Top Who We Are What We Do Our Work Latest Ideas Data Studio Our Solutions Our Partners Careers News Contact [email protected] Connect with us: Privacy Policy © 2025 Velir | 2026-01-13T09:29:41 |
https://support.microsoft.com/pt-pt/microsoft-store-and-billing | Ajuda da Microsoft Store e faturação Avançar para o conteúdo principal Microsoft Suporte Suporte Suporte Home Page Microsoft 365 Office Produtos Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows mais... Dispositivos Surface Acessórios para PC Xbox Jogos de PC HoloLens Surface Hub Garantias de hardware Conta e faturação Conta Microsoft Store e faturação Recursos Novidades Fóruns da comunidade Administradores do Microsoft 365 Portal para Pequenas Empresas Programador Educação Comunicar uma fraude de suporte técnico Segurança do produto Mais Comprar o Microsoft 365 Toda a Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Promoções Pequena Empresa Suporte Software Software Aplicações do Windows IA OneDrive Outlook Mudança do Skype para o Teams OneNote Microsoft Teams PCs e dispositivos PCs e dispositivos Comprar a Xbox Acessórios Entretenimento Entretenimento Xbox Game Pass Ultimate Xbox e jogos Jogos para PC Negócios Negócios Microsoft Security Azure Dynamics 365 Microsoft 365 para empresas Microsoft Industry Microsoft Power Platform Windows 365 Desenvolvedor & it Desenvolvedor & it Programador Microsoft Microsoft Learn Suporte para aplicações do marketplace de IA Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Outros Outros Transferências gratuitas e segurança Educação Cartões de oferta da Microsoft Licenciamento Ver mapa do Site Procurar Procurar ajuda Sem resultados Cancelar Iniciar sessão Iniciar sessão com a Microsoft Iniciar sessão ou criar uma conta. Olá, Selecione uma conta diferente. Tem várias contas Selecione a conta com a qual pretende iniciar sessão. Ajuda da Microsoft Store e faturação Gerir subscrições Devolve & reembolsos Opções de pagamento Histórico de encomendas Cartões de oferta Instalar o Microsoft 365 Microsoft Store no Windows Explorar os serviços da Microsoft Store Desde envio gratuito e regressos à nossa proteção de preços de 60 dias, estamos aqui para ajudá-lo a fazer mais com os melhores dispositivos, software, jogos e recursos. Veja o que a Microsoft Store tem para oferecer: Suporte para compras e compras | Configuração e formação do produto | Suporte para pequenas empresas Suporte para compras e compras Os serviços da Microsoft Store não estão disponíveis em todas as regiões. Para ver que opções estão disponíveis para si, selecione o seu país ou região na lista pendente abaixo e, se não estiver listado, selecione Outras regiões . Selecione a sua região Estados Unidos Austrália Canadá (inglês) Canadá (francês) Reino Unido Outras regiões Porquê fazer compras na Microsoft Store Compras fáceis e convenientes Envio gratuito de 2 a 3 dias Devoluções gratuitas de 60 dias Proteção de preços de 60 dias Opções de pagamento flexíveis Dinheiro para o seu dispositivo utilizado Troca e reciclagem Descontos e ofertas especiais Para estudantes, encarregados de educação e educadores Para militares Proteção alargada de dispositivos Plano de proteção do Microsoft Complete Podemos ajudá-lo a encontrar o que precisa Ajuda do suporte de vendas Answer desk para pessoas com deficiência Comprar com um associado ASL Porquê fazer compras na Microsoft Store Compras fáceis e convenientes Envio gratuito Devoluções gratuitas de 60 dias Proteção de preços de 60 dias Dinheiro para o seu dispositivo utilizado Troca e reciclagem Descontos e ofertas especiais Para estudantes, encarregados de educação e educadores Podemos ajudá-lo a encontrar o que precisa Ajuda do suporte de vendas Answer desk para pessoas com deficiência Porquê fazer compras na Microsoft Store Compras fáceis e convenientes Envio gratuito Devoluções gratuitas de 60 dias Proteção de preços de 60 dias Dinheiro para o seu dispositivo utilizado Troca e reciclagem Descontos e ofertas especiais Para estudantes, encarregados de educação e educadores Proteção alargada de dispositivos Plano de proteção do Microsoft Complete Podemos ajudá-lo a encontrar o que precisa Se tiver dúvidas antes de comprar, converse com um especialista em produtos ou marque um compromisso de compras. Ajuda do suporte de vendas Porquê fazer compras na Microsoft Store Compras fáceis e convenientes Envio gratuito Devoluções gratuitas de 60 dias Proteção de preços de 60 dias Dinheiro para o seu dispositivo utilizado Troca e reciclagem Descontos e ofertas especiais Para estudantes, encarregados de educação e educadores Proteção alargada de dispositivos Plano de proteção do Microsoft Complete Porquê fazer compras na Microsoft Store Compras fáceis e convenientes Envio gratuito Devoluções gratuitas de 60 dias Proteção de preços de 60 dias Dinheiro para o seu dispositivo utilizado Troca e reciclagem Descontos e ofertas especiais Para estudantes, encarregados de educação e educadores Podemos ajudá-lo a encontrar o que precisa Ajuda do suporte de vendas Answer desk para pessoas com deficiência Porquê fazer compras na Microsoft Store Podemos ajudá-lo a encontrar o que precisa Se tiver dúvidas antes de comprar, converse com um especialista em produtos. Ajuda do suporte de vendas Procurar na Microsoft Store The Microsoft Store Configuração e formação do produto Nem todos os serviços da Microsoft Store listados aqui estão disponíveis em todas as regiões. Para ver as suas opções, selecione o seu país ou região na lista pendente abaixo: Selecione a sua região Estados Unidos Austrália Canadá (inglês) Canadá (francês) Reino Unido Outras regiões Ajuda e recursos de aprendizagem Consulte os nossos recursos de suporte de produtos para o ajudar a encontrar as respostas de que precisa. Dispositivos Surface | Xbox Microsoft 365 | Windows Ajuda e recursos de aprendizagem Os nossos recursos de suporte de produtos estão aqui para o ajudar a encontrar as respostas de que precisa. Dispositivos Surface | Xbox Microsoft 365 | Windows Ajuda e recursos de aprendizagem Consulte os nossos recursos de suporte de produtos para o ajudar a encontrar as respostas de que precisa. Dispositivos Surface | Xbox Microsoft 365 | Windows Ajuda e recursos de aprendizagem Consulte os nossos recursos de suporte de produtos para o ajudar a encontrar as respostas de que precisa. Dispositivos Surface | Xbox Microsoft 365 | Windows Ajuda e recursos de aprendizagem Consulte os nossos recursos de suporte de produtos para o ajudar a encontrar as respostas de que precisa. Dispositivos Surface | Xbox Microsoft 365 | Windows Ajuda e recursos de aprendizagem Consulte os nossos recursos de suporte de produtos para o ajudar a encontrar as respostas de que precisa. Dispositivos Surface | Xbox Microsoft 365 | Windows Suporte para pequenas empresas Para ver que opções de suporte para pequenas empresas estão disponíveis na sua região, selecione o seu país ou região na lista pendente abaixo: Selecione a sua região Estados Unidos Austrália Canadá (inglês) Canadá (francês) Reino Unido Outras regiões Recursos para a sua pequena empresa Receba conselhos, formação gratuita, produtos e ferramentas para ajudar o seu negócio a florescer. Ajuda e aprendizagem para pequenas empresas Centro de Recursos de Pequenas Empresas Recursos para a sua pequena empresa Receba conselhos, formação gratuita, produtos e ferramentas para ajudar o seu negócio a florescer. Ajuda e aprendizagem para pequenas empresas Centro de Recursos de Pequenas Empresas Recursos para a sua pequena empresa Receba conselhos, formação gratuita, produtos e ferramentas para ajudar o seu negócio a florescer. Ajuda e aprendizagem para pequenas empresas Centro de recursos de pequenas empresas Recursos para a sua pequena empresa Na avaliação das necessidades da sua empresa para ajudar na configuração e na resolução de problemas, estamos aqui para ajudar. Receba conselhos, formação gratuita, produtos e ferramentas para ajudar o seu negócio a florescer. Ajuda e aprendizagem para pequenas empresas Centro de recursos de pequenas empresas Recursos para a sua pequena empresa Receba conselhos, formação gratuita, produtos e ferramentas para ajudar o seu negócio a florescer. Ajuda e aprendizagem para pequenas empresas Centro de Recursos de Pequenas Empresas Recursos para a sua pequena empresa Receba conselhos, formação gratuita, produtos e ferramentas para ajudar o seu negócio a florescer. Ajuda e aprendizagem para pequenas empresas Novidades Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot para organizações Copilot para uso pessoal Microsoft 365 Explorar produtos Microsoft Aplicações do Windows 11 Microsoft Store Perfil da conta Centro de Transferências Suporte da Microsoft Store Devoluções Controlo de encomendas Reciclagem Garantias Comercias Educação Microsoft Educação Dispositivos para educação Microsoft Teams para Educação Microsoft 365 Educação Office Educação Formação e desenvolvimento de educadores Promoções para estudantes e pais Azure para estudantes Empresa Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft 365 Copilot Microsoft Teams Pequena Empresa Programador e TI Programador Microsoft Microsoft Learn Suporte para aplicações do marketplace de IA Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Empresa Carreiras Acerca da Microsoft Notícias da empresa Privacidade na Microsoft Investidores Sustentabilidade Português (Portugal) Ícone de Optar por Não Participar em As Suas Opções de Privacidade As suas Escolhas de Privacidade Ícone de Optar por Não Participar em As Suas Opções de Privacidade As suas Escolhas de Privacidade Privacidade da Saúde do Consumidor Contactar a Microsoft Privacidade Gerir cookies Termos de utilização Marcas Registadas Acerca dos nossos anúncios EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:29:41 |
https://git-scm.com/book/tr/v2/Git-Temelleri-Uzak-Repo-ile-%c3%87al%c4%b1%c5%9fmak | Git - Uzak Repo ile Çalışmak About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Başlangıç 1.1 Sürüm Denetimi 1.2 Git’in Kısa Tarihçesi 1.3 Git Nedir? 1.4 Komut Satırı 1.5 Git’i Yüklemek 1.6 Git’i İlk Defa Kurmak 1.7 Yardım Almak 1.8 Özet 2. Git Temelleri 2.1 Bir Git Reposu Oluşturma/Kopyalama 2.2 Değişikliklerin Repoya Kaydedilmesi 2.3 Katkı Geçmişini Görüntüleme 2.4 Değişiklikleri Geri Alma 2.5 Uzak Repo ile Çalışmak 2.6 Etiketleme 2.7 Komut Kısayolu (Alias) Ayarlama 2.8 Özet 3. Git Dalları 3.1 Dallar 3.2 Kısaca Dallandırma ve Birleştirme Temelleri 3.3 Dal Yönetimi 3.4 İş Akışı Dallandırması 3.5 Uzak Dallar 3.6 Yeniden Temelleme (rebase) 3.7 Özet 4. Bir Sunucuda Git Kurma 4.1 İletişim Kuralları (Protocols) 4.2 Bir Sunucuda Git Kurma 4.3 SSH Ortak Anahtarınızı Oluşturma 4.4 Sunucu Kurma 4.5 Git Cini (Daemon) 4.6 Akıllı HTTP 4.7 GitWeb 4.8 GitLab 4.9 Üçüncü Taraf Barındırma (Hosting) Seçenekleri 4.10 Özet 5. Dağıtık Git 5.1 Dağıtık İş Akışları 5.2 Projenin Gelişiminde Rol Almak 5.3 Bir Projeyi Yürütme 5.4 Özet 6. GitHub 6.1 Bir Projeye Katkıda Bulunmak 6.2 Proje Bakımı 6.3 Kurumsal Yönetim 6.4 GitHub’ı otomatikleştirme 6.5 Özet 7. Git Araçları 7.1 Düzeltme Seçimi 7.2 Etkileşimli İzlemleme (Staging) 7.3 Saklama ve Silme 7.4 Çalışmanızı İmzalama 7.5 Arama 7.6 Geçmişi Yeniden Yazma 7.7 Reset Komutunun Gizemleri 7.8 İleri Seviye Birleştirme 7.9 Rerere 7.10 Git’le Hata Ayıklama 7.11 Alt Modüller 7.12 Demetleme (Bundling) 7.13 Git Nesnesini Değiştirme 7.14 Kimlik Bilgisi Depolama 7.15 Özet 8. Git’i Özelleştirmek 8.1 Git Yapılandırması 8.2 Git Nitelikleri 8.3 Git Kancaları (Hooks) 8.4 Bir Örnek: Mecburi Git Politikası 8.5 Özet 9. Git ve Diğer Sistemler 9.1 İstemci Olarak Git 9.2 Git’e Geçiş 9.3 Özet 10. Dahili Git Ögeleri 10.1 Tesisat ve Döşeme (Plumbing ve Porcelain) 10.2 Git Nesneleri 10.3 Git Referansları 10.4 Packfiles 10.5 Refspec 10.6 Transfer Protokolleri 10.7 Bakım ve Veri Kurtarma 10.8 Ortam Değişkenleri 10.9 Özet A1. Ek bölüm A: Diğer Ortamlarda Git A1.1 Görsel Arayüzler A1.2 Visual Studio ile Git A1.3 Visual Studio Code ile Git A1.4 Eclipse ile Git A1.5 Sublime Text ile Git A1.6 Bash ile Git A1.7 Zsh ile Git A1.8 PowerShell ile Git A1.9 Özet A2. Ek bölüm B: Git’i Uygulamalarınıza Gömmek A2.1 Git Komut Satırı A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Ek bölüm C: Git Komutları A3.1 Kurulum ve Yapılandırma Komutları A3.2 Proje Oluşturma Komutları A3.3 Kısaca Poz (Snapshot) Alma A3.4 Dallandırma ve Birleştirme Komutları A3.5 Projeleri Paylaşma ve Güncelleme Komutları A3.6 İnceleme ve Karşılaştırma Komutları A3.7 Hata Ayıklama (Debugging) Komutları A3.8 Yamalama (Patching) A3.9 E-Posta Komutları A3.10 Harici Sistemler A3.11 Yönetim A3.12 Tesisat (Plumbing) Komutları 2nd Edition 2.5 Git Temelleri - Uzak Repo ile Çalışmak Uzak Repo ile Çalışmak Herhangi bir Git projesinde işbirliği yapabilmek için uzak repolarınızı nasıl yöneteceğinizi bilmeniz gerekir. Uzak repolar, projenizin İnternette veya ağda bir yerde barındırılan sürümleridir. Bunlardan birkaçına sahip olabilirsiniz. Bunların her biri genellikle sizin için salt okunur veya okuma/yazma erişimlidir. Başkalarıyla işbirliği yapmak, bu uzak repoları yönetmeyi ve işlerinizi paylaşmanız gerektiğinde verileri bu havuzlara gönderip almayı içerir. Uzak repoların yönetilmesi; uzak repoların nasıl ekleneceğini, artık geçerli olmayan uzak sunucuların nasıl kaldırılacağını, çeşitli uzak dalların nasıl yönetileceğini, bunların izlenip izlenmediğini nasıl tanımlayacağınızı ve daha fazlasını bilmeyi gerektirir. Bu bölümde bu uzaktan yönetim becerilerinden bazılarını ele alacağız. Not Uzak repolar yerel makinenizde olabilir. Aslında sizinle aynı ana bilgisayar üzerinde olan bir ``uzak`` repoyla çalışıyor olmanız tamamen mümkündür. Uzak kelimesi, veri deposunun ağda veya internette başka bir yerde olduğu anlamına gelmez, yalnızca başka bir yerde olduğu anlamına gelir. Böyle bir uzak repoyla çalışmak, diğer uzaktan sunucularda olduğu gibi yine de tüm standart itme (push), çekme (pull) ve getirme (fetch) işlemlerini içerecektir. Uzak Sunucuları Görme Hangi uzak sunucuları yapılandırdığınızı görmek için git remote komutunu çalıştırabilirsiniz. Bu belirttiğiniz her uzak sunucunun kısa adlarını listeler. Reponuzu kopyaladıysanız en azından ``Origin`’i görmelisiniz (Git’in kopyaladığınız sunucuya verdiği varsayılan isim budur): $ git clone https://github.com/schacon/ticgit Cloning into 'ticgit'... remote: Reusing existing pack: 1857, done. remote: Total 1857 (delta 0), reused 0 (delta 0) Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done. Resolving deltas: 100% (772/772), done. Checking connectivity... done. $ cd ticgit $ git remote origin Ayrıca Git’in o uzak sunucuya okuma ve yazma sırasında kullanılacak kısa ad için sakladığı URL’leri gösteren -v bayrağını da belirtebilirsiniz: $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) Birden fazla uzak sunucunuz varsa, bu komut hepsini listeler. Örneğin, birden fazla geliştiricinin beraber çalışmak için oluşturduğu birden fazla uzak sunucuya sahip bir repo şöyle görünebilir. $ cd grit $ git remote -v bakkdoor https://github.com/bakkdoor/grit (fetch) bakkdoor https://github.com/bakkdoor/grit (push) cho45 https://github.com/cho45/grit (fetch) cho45 https://github.com/cho45/grit (push) defunkt https://github.com/defunkt/grit (fetch) defunkt https://github.com/defunkt/grit (push) koke git://github.com/koke/grit.git (fetch) koke git://github.com/koke/grit.git (push) origin git@github.com:mojombo/grit.git (fetch) origin git@github.com:mojombo/grit.git (push) Bu, diğer geliştiricilerden kolaylıkla katkı alabileceğimiz anlamına gelir. Ayrıca bunlardan bir veya daha fazlasını zorlama iznimiz olabilir, ancak bu ekrandan bu çıkarımda bulunmak mümkün değil. Bu uzak sunucuların çeşitli protokoller kullandığına dikkat edin (Bu konu hakkında daha fazla bilgiyi Bir Sunucuda Git Kurma bölümünde ele alacağız). Uzak Sunucuları Görme git clone komutunun sizin için ``Origin`` uzak sunucusunu nasıl eklediğinden üstü kapalı bahsettik ve bazı gösterimler verdik. Yeni bir uzak sunucunun nasıl ekleneceği aşağıda daha açıkça anlatılmıştır. Kısa adını kullanarak yeni bir uzak Git reposu eklemek için git remote add <shortname> <url> komutunu çalıştırın: $ git remote origin $ git remote add pb https://github.com/paulboone/ticgit $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) pb https://github.com/paulboone/ticgit (fetch) pb https://github.com/paulboone/ticgit (push) Artık komut satırında URL’nin tamamı yerine pb dizesini kullanabilirsiniz. Örneğin, Paul’un sahip olduğu ancak henüz sizin reponuzda bulunmayan tüm kodları getirmek istiyorsanız, git fetch pb komutunu çalıştırabilirsiniz: $ git fetch pb remote: Counting objects: 43, done. remote: Compressing objects: 100% (36/36), done. remote: Total 43 (delta 10), reused 31 (delta 5) Unpacking objects: 100% (43/43), done. From https://github.com/paulboone/ticgit * [new branch] master -> pb/master * [new branch] ticgit -> pb/ticgit Paul’un ana-dalına (master branch) artık yerelde pb/master olarak erişilebilmektedir. Onu kendi dallarınızdan biriyle birleştirebilirsiniz veya incelemek isterseniz herhangi bir dala geçerek göz atabilirsiniz. (Dalların ne olduğunu ve bunların nasıl kullanılacağını Git Dalları bölümünde çok daha ayrıntılı olarak ele alacağız.) Uzak Sunucudan Getirme ve Çekme Az önce gördüğünüz gibi uzak projelerinizden veri almak için aşağıdaki komutu çalıştırabilirsiniz: $ git fetch <remote> Komut o uzak projeye gider ve o uzak projeden henüz sahip olmadığınız tüm verileri çeker. Bunu yaptığınız takdirde, o uzak sunucudaki tüm dallara erişim için gerekli referanslara sahip olacaksınız. Böylece istediğiniz zaman kodları inceleyebilir veya kendi kodunuzla birleştirebilirsiniz. Eğer bir repoyu kopyalarsanız, komut o uzak repoyu otomatik olarak ``Origin`` adı altına ekler. Yani, git fetch origin , kopyalamanızdan (veya sunucudan son getirmenizden) bu yana sunucuya gönderilen tüm yeni çalışmaları getirir. git fetch komutunun verileri yalnızca yerel reponuza indirdiğini unutmamalısınız. Verileri herhangi bir çalışmanızla otomatik olarak birleştirmez veya üzerinde çalışmakta olduğunuz kodu değiştirmez. Hazır olduğunuzda bunu manuel olarak kendi kodunuzla birleştirmeniz gerekir. Geçerli dalınız uzak bir dalı izleyecek şekilde ayarlanmışsa (daha fazla bilgi için sonraki bölüme ve Git Dalları 'e bakın), bu değişiklikleri otomatik olarak getirmek için git pull komutunu kullanabilirsiniz. Daha sonra bu uzak dalı mevcut dalınızla birleştirin. Bu size daha kolay veya daha rahat bir iş akışı sağlar. Varsayılan olarak git clone komutu, yerel ana dalınızı (genellikle main veya master olarak adlandırılır), kopyaladığınız uzak sunucudaki uzak ana dalı (veya varsayılan dalın adı her neyse) izleyecek şekilde otomatik olarak ayarlar. git pull komutunu çalıştırmak genellikle verileri kopyaladığınız asıl sunucudan getirir ve otomatik olarak bu verileri üzerinde çalışmakta olduğunuz kodla birleştirmeye çalışır. Kodlarınızı Uzak Sunucuya İtmek Projeniz belli bir aşamaya ulaştıktan sonra paylaşmak isteyebilirsiniz. Bunun için geliştirilmiş kodunuzu uzak repoya itmeniz gerekmektedir. Bunun için kullanmanız gereken komut basittir: git Push <remote> <branch> . Ana dalınızı Origin sunucunuza göndermek istiyorsanız (yine kopyalama genellikle bu adların her ikisini de sizin için otomatik olarak ayarlar), o zaman işlediğiniz katkıları sunucuya geri göndermek için şunu çalıştırabilirsiniz: $ git push origin master Bu komut yalnızca yazma erişiminizin olduğu bir sunucudan kopyalama yapmışsanız ve bu arada hiç kimse başka bir itme yapmamışsa çalışır. Siz ve başkaları projeyi aynı anda kopyalarsanız ve diğerleri sizden da önce değiştirilmiş kodlarını uzak sunucuya gönderirse, doğal olarak sizin itmeniz reddedilecektir. Değiştirilmiş kodunuzu itmenize izin verilmeden önce, diğerleri tarafından güncellenmiş kodları uzak repodan getirmeniz ve kendi işinize dahil etmeniz gerekecek. Güncel çalışmanızı uzak sunuculara nasıl gönderebileceğiniz hakkında daha ayrıntılı bilgi için Git Dalları konusuna bakın. Uzak Sunucunun İncelenmesi Belirli bir uzak sunucu hakkında daha fazla bilgi görmek istiyorsanız git remote show <remote> komutunu kullanabilirsiniz. Bu komutu origin gibi belirli bir kısa adla çalıştırırsanız şöyle bir sonuç elde edersiniz: $ git remote show origin * remote origin Fetch URL: https://github.com/schacon/ticgit Push URL: https://github.com/schacon/ticgit HEAD branch: master Remote branches: master tracked dev-branch tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) Bu komut uzak repo URL’si yanında izlenen dal bilgilerini de listeler. Bununla birlikte size, eğer ana daldaysanız (main veya master) ve git pull çalıştırırsanız, tüm uzak referansları getirdikten sonra otomatik olarak uzak repodaki ana dalla birleşeceğini söyler. Ayrıca çekme yaptığı tüm uzak referansları da listeler. Bu karşılaşacağınız basit bir örnektir. Ancak Git’i daha yoğun kullandığınızda, git remote show komutuyla çok daha fazla bilgi görebilirsiniz: $ git remote show origin * remote origin URL: https://github.com/my-org/complex-project Fetch URL: https://github.com/my-org/complex-project Push URL: https://github.com/my-org/complex-project HEAD branch: master Remote branches: master tracked dev-branch tracked markdown-strip tracked issue-43 new (next fetch will store in remotes/origin) issue-45 new (next fetch will store in remotes/origin) refs/remotes/origin/issue-11 stale (use 'git remote prune' to remove) Local branches configured for 'git pull': dev-branch merges with remote dev-branch master merges with remote master Local refs configured for 'git push': dev-branch pushes to dev-branch (up to date) markdown-strip pushes to markdown-strip (up to date) master pushes to master (up to date) Bu komut belirli bir daldayken git Push komutunu çalıştırdığınızda, otomatik olarak hangi dalın uzak repoya aktarılacağını gösterir. Ayrıca; sunucudaki hangi uzak dallara henüz sahip olmadığınızı, yerelde sahip olduğunuz hangi dalların uzak sunucudan kaldırılmış olduğunu ve git pull çalıştırdığınızda otomatik olarak uzak-izleme dallarıyla birleşecek çoklu yerel dallarınızı da gösterir. Uzak Sunucuları Yeniden Adlandırma ve Kaldırma Bir uzaktan sunucunun kısa adını değiştirmek için git remote rename komutunu çalıştırabilirsiniz. Örneğin pb`yi `paul olarak yeniden adlandırmak istiyorsanız, bunu git remote rename komutu ile yapabilirsiniz: $ git remote rename pb paul $ git remote origin paul Bunun tüm uzaktan izleme dal adlarınızı değiştirdiğini belirtmekte fayda var. Önceden pb/master olarak adlandırılan (referans) uzak sunucunun yeni adı artık `paul/master`dır. Herhangi bir nedenden dolayı uzak sunucuyu kaldırmak isterseniz (ör: sunucuyu taşımışsanız veya artık belirli bir aynayı (mirror: bir repodaki tüm verileri ve geçmişi eksiksiz olarak başka bir repoya kopyalayan bir repo) kullanmıyorsanız veya geliştiricilerden biri artık projeye katkıda bulunmuyorsa git remote remove veya git remote rm komutlarından birini kullanabilirsiniz: $ git remote remove paul $ git remote origin Bir uzaktan sunucunun referansını bu şekilde sildiğinizde, o sunucuyla ilişkili tüm uzaktan izleme dalları ve yapılandırma ayarları da silinir. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://www.youtube.com/?tab=i1 | YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T09:29:41 |
https://support.smartbear.com/reflect/docs/en/api/tests-api.html#get-execution-status-2110494 | Tests API | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Developer API Tests API Tests API Execute tests and get the status of individual test runs. List all tests Returns a list of test descriptions containing the test’s id, name, created timestamp and folders. REQUEST GET https://api.reflect.run/v1/tests RESPONSE { "tests": [ { "id": 3072323, "name": "Registration Flow", "created": 1570546969108, "folders": [ "regression-tests" ] } ] } RESPONSE FIELDS tests object: A list of test descriptions, including the test's id, name and folders. Run a test Immediately schedules a test. The browser field allows you to specify the browser to run the test with. Supported values are: Chrome , Edge , Firefox , and Safari - if no value is specified Chrome is used. Note Your account must have access to the requested browser - requesting an unsupported browser will return a 400 error code. Reflect identifies certain properties of the execution as “reserved”. These reserved fields can be overridden with values provided by the API request: hostnames : Allows you to specify a replacement hostname value for a given target hostname. You can also optionally specify a new port by including it in the replacement (see below for an example). If your override specifies a port, note the following behavior: If original includes a port value, it will only be applied on URLs of the test that also use that same port. For example, an original value of example.com:1234 would have no effect on https://example.com or https://example.com:5678. If original does not include a port value, it will match every URL of the test that uses the same hostname, regardless of port. For example, an original value of example.com would match both https://example.com and https://example.com:1234. If a port was specified in the URL of the test, it will be preserved unless a new value is specified in replacement or original included the port and replacement did not - in that case no port would be included in the resulting URL. agent : Allows you to select a specific Tunnel to run the test through by specifying the agent’s name. parameters : Allows you to specify a URL parameter key/value pair that will be included (or overwritten) on the test’s initial URL. cookies : Allows you to specify cookies that will be set when loading the test’s initial URL. A cookie consists of the following fields: name (required string): The name of the cookie to be set. value (required string): The cookie’s value. domain (optional string): Host to which the cookie will be sent. Defaults to the host of the test’s initial URL. expires (optional number): Epoch timestamp (in milliseconds) indicating when the cookie should be deleted. If unspecified, the cookie becomes a session cookie. httpOnly (optional boolean): Indicates the cookie should be inaccessible to JavaScript on the page and only sent to the server. maxAge (optional number): Number of milliseconds until the cookie expires. If both expires and maxAge are set, maxAge has precedence. path (optional string): A URL path that must exist in a request URL in order to include the cookie in a request. secure (optional boolean): Indicates that the cookie should only be sent to the server when a request is made with https: . headers : Allows you to specify headers that will be sent when loading the test’s initial URL. name (required string): The name of the header. value (required string): The header value. persist (optional boolean): Specifies whether this header should only be set in the initial request or for every subsequent HTTP request (ex: when overriding the Accept-Language header). If set to true , the Authorization header is only set for requests that match the hostname of the test’s original URL. Defaults to false . localStorage and sessionStorage : Allows you to specify local and session storage values to be set on the test’s initial URL. The variables field allows you to specify a definition for a variable used in the test. REQUEST POST https://api.reflect.run/v1/tests/<test-id>/executions { "browser": "Chrome", "overrides": { "agent": { "name": "agent-name" }, "hostnames": [{ "original": "prod.myapp.com", "replacement": "staging.myapp.com:1234" }], "parameters": [{ "key": "token", "value": "abcdef" }], "cookies": [{ "name": "my-favorite-cookie", "value": "chocolate-chip", "domain": "myapp.com", "expires": 123456789, "httpOnly": false, "maxAge": 123, "path": "/", "secure": true }], "headers": [{ "name": "X-Custom-Header", "value": "custom-value" }], "localStorage": [{ "key": "my-local-key", "value": "local-value" }], "sessionStorage": [{ "key": "my-session-key", "value": "session-value" }] }, "variables": { "username1": "user+${alpha(8)}@example.com", "password": "acompletelyunguessablepassword" }, "emailFailures": true } REQUEST FIELDS overrides optional object: Overrides to apply to properties of the test being executed. agent (object, optional) name (string, required) — The name of the Tunnel/Agent to use for this execution. variables optional object: Collection of ('name', 'definition') variable overrides to apply to this scheduled execution. emailFailures optiona boolean: Controls whether email notifications should be sent for a failed test run. The default is true. RESPONSE { "executionId": 8939 } RESPONSE FIELDS executionId number: An identifier for the scheduled execution created by the request. Get execution status Returns a list of test result objects. The test result object includes the test’s id and a status field describing whether the test is “queued”, “running”, “succeeded”, or “failed”. Additionally, it contains a run object describing the properties of the test run such as its starting and ending time, and its video URL. REQUEST GET https://api.reflect.run/v1/executions/<execution-id> RESPONSE { "executionId": 17671, "browser": "Edge", "tests": [ { "testId": 1690, "status": "succeeded", "run": { "runId": 690, "status": "passed", "variables": {}, "startTime": 1654632014295, "endTime": 1654632027297, "runTime": 13002, "videoUrl": "https://reflect-videos.s3.amazonaws.com/690_89f4.mp4" } } ] } RESPONSE FIELDS executionId number: An identifier for the scheduled execution. browser string: The browser that the tests in the scheduled execution are configured to run on. tests object: List of test results, including the testId and status. tests.testId number: An identifier for the test. tests.status string: One of: queued, running, succeeded, or failed. Summarizes the outcome of the test instance from its runs. tests.run object: The test run from this execution. tests.run.runId number: An identifier for the test run. tests.run.status string: The outcome of the test run. Either passed or failed. tests.run.variables object: The variables that were used or created by the test run. tests.run.startTime number: Timestamp of when the test run started. tests.run.endTime number: Timestamp of when the test run stopped. tests.run.runTime number: Total time that the test run spent running (endTime - startTime). tests.run.videoUrl string: The URL of a video recording of the test run. In this section : Tests API List all tests Run a test Get execution status Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:41 |
https://trello.com/de/home#video | Erfasse, organisiere und erledige deine Aufgaben von überall aus | Trello Weiter zum Hauptinhalt Funktionen Lösungen Tarife Preise Ressourcen Entdecke die Features, die deinem Team zum Erfolg verhelfen Eingang Erfasse alle wichtigen Details aus E-Mails, Slack und mehr direkt in deinem Trello-Posteingang. Planer Synchronisiere deinen Kalender und weise Zeitfenster für konzentriertes Arbeiten zu, um die Produktivität zu steigern. Automatisierung Automatisiere Aufgaben und Workflows mit Trello. Power-Ups Power-Up für deine Teams: Verknüpfe ihre Lieblingstools mit Trello-Plugins! Vorlagen Gib deinem Team eine Blaupause für den Erfolg mit benutzerfreundlichen Vorlagen von branchenführenden Unternehmen und der Trello-Community. Integrationen Finde Apps, die dein Team bereits nutzt, oder entdecke neue Möglichkeiten, um deine Arbeit in Trello zu erledigen. Lerne Trello kennen Trello hilft deinem Team bei der Arbeit. Unabhängig vom Projekt, Workflow oder Team – mit Trello kannst du alles organisieren. Es ist ganz einfach! Registriere dich, erstelle ein Board und schon kann es losgehen. Trello kennenlernen Unsere Trello-Playbooks eignen sich für Teams aller Art – lass dich inspirieren! Marketingteams Egal, ob es um die Produkteinführung, eine Kampagne oder die Erstellung neuer Inhalte geht – Trello verhilft Marketingteams zum Erfolg. Produktmanagement Verwende die Management-Boards und Roadmap-Funktionen von Trello, um komplexe Projekte und Prozesse zu vereinfachen. Engineering-Teams Mit Trello kannst du schneller mehr Code liefern und die Agilität deines Entwicklerteams verbessern. Designteams Unterstütze deine Designteams mit Trello, um kreative Anfragen und die teamübergreifende Zusammenarbeit zu verbessern. Start-ups Vom Erreichen der Umsatzziele bis hin zur Verwaltung von Workflows – kleine Unternehmen profitieren von Trello. Remote-Teams Sorge dafür, dass dein Remote-Team in Verbindung und motiviert bleibt, egal, wo auf der Welt sich deine Mitarbeiter befinden. Alle Teams anzeigen Unser Produkt in der Praxis Anwendungsbeispiel: Aufgabenmanagement Aufgabenverfolgung mit dem gewissen Etwas – überwache den Fortschritt deiner Aufgaben zentral in einer praktischen Ansicht. Anwendungsfall: zentrale Ressourcenverwaltung Spart euch jede Menge Zeit, indem deine Teams benötigte Informationen schnell und einfach an einem zentralen Ort finden. Anwendungsbeispiel: Projektmanagement Mit Trello kannst du Projekte organisieren, Fristen einhalten und Teamkollegen auf dem Laufenden halten. Alle Anwendungsbeispiele anzeigen Standard Für Teams, die mehr Aufgaben managen und die Zusammenarbeit skalieren müssen. Premium Ideal für Teams mit bis zu 100 Personen, die mehrere Projekte verfolgen und ihre Aufgaben auf unterschiedliche Weise visualisieren müssen. Enterprise Alles, was deine Enterprise-Teams und -Admins für das Projektmanagement brauchen. Free-Tarif Für Einzelpersonen oder kleine Teams, die ihre Aufgaben organisieren möchten. Trello entdecken Tarife und Preise vergleichen Egal, ob sich dein Team aus 2 oder 2.000 Personen zusammensetzt: Mit den flexiblen Preismodellen von Trello zahlst du nur für das, was du auch wirklich brauchst. Trello-Preisliste anzeigen Lernen und austauschen Trello-Leitfaden Unser einfacher Workflow-Leitfaden unterstützt dich bei der Projekteinrichtung und macht dich in Nullkommanichts zum Trello-Experten! Leitfaden für die Remote-Arbeit Ein umfassender Leitfaden zum Aufbau erfolgreicher Remote-Teams Webinare Sieh dir unsere kostenlosen Trello-Webinare an und werde ein Produktivitätsprofi. Kundenberichte Erfahre aus erster Hand, wie Unternehmen Trello als wichtigen Teil ihres Workflows einsetzen. Entwickler Dieses Power-Up bietet dir unzählige Möglichkeiten, Trello-Benutzern genau das zu liefern, was sie brauchen. Hilfreiche Ressourcen Benötigst du Hilfe? Unsere Artikel und FAQs helfen dir weiter. Zurück Navigation Funktionen Lösungen Tarife Preise Ressourcen Entdecke die Features, die deinem Team zum Erfolg verhelfen Eingang Erfasse alle wichtigen Details aus E-Mails, Slack und mehr direkt in deinem Trello-Posteingang. Planer Synchronisiere deinen Kalender und weise Zeitfenster für konzentriertes Arbeiten zu, um die Produktivität zu steigern. Automatisierung Automatisiere Aufgaben und Workflows mit Trello. Power-Ups Power-Up für deine Teams: Verknüpfe ihre Lieblingstools mit Trello-Plugins! Vorlagen Gib deinem Team eine Blaupause für den Erfolg mit benutzerfreundlichen Vorlagen von branchenführenden Unternehmen und der Trello-Community. Integrationen Finde Apps, die dein Team bereits nutzt, oder entdecke neue Möglichkeiten, um deine Arbeit in Trello zu erledigen. Lerne Trello kennen Trello hilft deinem Team bei der Arbeit. Unabhängig vom Projekt, Workflow oder Team – mit Trello kannst du alles organisieren. Es ist ganz einfach! Registriere dich, erstelle ein Board und schon kann es losgehen. Trello kennenlernen Unsere Trello-Playbooks eignen sich für Teams aller Art – lass dich inspirieren! Marketingteams Egal, ob es um die Produkteinführung, eine Kampagne oder die Erstellung neuer Inhalte geht – Trello verhilft Marketingteams zum Erfolg. Produktmanagement Verwende die Management-Boards und Roadmap-Funktionen von Trello, um komplexe Projekte und Prozesse zu vereinfachen. Engineering-Teams Mit Trello kannst du schneller mehr Code liefern und die Agilität deines Entwicklerteams verbessern. Designteams Unterstütze deine Designteams mit Trello, um kreative Anfragen und die teamübergreifende Zusammenarbeit zu verbessern. Start-ups Vom Erreichen der Umsatzziele bis hin zur Verwaltung von Workflows – kleine Unternehmen profitieren von Trello. Remote-Teams Sorge dafür, dass dein Remote-Team in Verbindung und motiviert bleibt, egal, wo auf der Welt sich deine Mitarbeiter befinden. Alle Teams anzeigen Unser Produkt in der Praxis Lies dir unsere Anwendungsbeispiele durch, um Trello in deinem Team optimal zu nutzen. Alle Anwendungsbeispiele anzeigen Standard Für Teams, die mehr Aufgaben managen und die Zusammenarbeit skalieren müssen. Premium Ideal für Teams mit bis zu 100 Personen, die mehrere Projekte verfolgen und ihre Aufgaben auf unterschiedliche Weise visualisieren müssen. Enterprise Alles, was deine Enterprise-Teams und -Admins für das Projektmanagement brauchen. Free-Tarif Für Einzelpersonen oder kleine Teams, die ihre Aufgaben organisieren möchten. Trello entdecken Tarife und Preise vergleichen Egal, ob sich dein Team aus 2 oder 2.000 Personen zusammensetzt: Mit den flexiblen Preismodellen von Trello zahlst du nur für das, was du auch wirklich brauchst. Trello-Preisliste anzeigen Lernen und austauschen Trello-Leitfaden Unser einfacher Workflow-Leitfaden unterstützt dich bei der Projekteinrichtung und macht dich in Nullkommanichts zum Trello-Experten! Leitfaden für die Remote-Arbeit Ein umfassender Leitfaden zum Aufbau erfolgreicher Remote-Teams Webinare Sieh dir unsere kostenlosen Trello-Webinare an und werde ein Produktivitätsprofi. Kundenberichte Erfahre aus erster Hand, wie Unternehmen Trello als wichtigen Teil ihres Workflows einsetzen. Entwickler Dieses Power-Up bietet dir unzählige Möglichkeiten, Trello-Benutzern genau das zu liefern, was sie brauchen. Hilfreiche Ressourcen Benötigst du Hilfe? Unsere Artikel und FAQs helfen dir weiter. Bessere Zusammenarbeit im Team Entdecke Trello-Anwendungsbeispiele, Produktivitätstipps, Best Practices für die Teamzusammenarbeit und Expertentipps für die Remote-Arbeit. Trello-Blog ansehen Accelerate your teams' work with AI features 🤖 now available for all Premium and Enterprise! Learn more. Erfasse, organisiere und erledige deine Aufgaben von überall aus. Entfliehe der Unordnung und dem Chaos und entfessele deine Produktivität mit Trello. Jetzt registrieren – es ist kostenlos! Durch Eingabe meiner E-Mail-Adresse erkenne ich die Datenschutzrichtlinie von Atlassian an. Video ansehen Hero Trello 1x1 Produktivität ohne Kompromisse Arbeite mit Posteingang, Boards und Planer organisiert und effizient. Jede Aufgabe, Idee oder Verpflichtung, sei sie auch noch so klein, findet ihren Platz, sodass du immer auf dem neuesten Stand bist. Eingang Vom Einfall direkt zum Element im Posteingang: Erfasse deine Aufgaben überall und jederzeit. Boards Eine lange Aufgabenliste ist eine Herausforderung, die sich meistern lässt. Behalte alles von Anfang bis Ende im Blick. Planer Ziehen, ablegen, erledigen: Trage deine wichtigsten Aufgaben in deinen Kalender ein und reserviere Zeit für das, was wirklich wichtig ist. Eingang Vom Einfall direkt zum Element im Posteingang: Erfasse deine Aufgaben überall und jederzeit. Boards Eine lange Aufgabenliste ist eine Herausforderung, die sich meistern lässt. Behalte alles von Anfang bis Ende im Blick. Planer Ziehen, ablegen, erledigen: Trage deine wichtigsten Aufgaben in deinen Kalender ein und reserviere Zeit für das, was wirklich wichtig ist. Von der Nachricht zur Aktion Wandele Nachrichten aus deinen bevorzugten Apps schnell in Aufgaben um und organisiere all deine Diskussionen und Aufgaben am selben Ort. E-MAIL-MAGIE Verwandele deine E-Mails ganz einfach in Aufgaben. Du musst sie dazu nur an deinen Trello-Posteingang weiterleiten, wo sie von Atlassian Intelligence (AI) in organisierte Aufgaben mit allen erforderlichen Links umgewandelt werden. SPEZIELLE FUNKTIONEN FÜR MESSAGING-APPS Du musst auf eine Nachricht aus Slack oder Microsoft Teams reagieren? Sende sie einfach direkt an dein Trello-Board. Über die Benutzeroberfläche deiner bevorzugten App kannst du Nachrichten aus deinem Trello-Posteingang mit KI-generierten Zusammenfassungen und Links speichern. Sorge für eine intelligente Arbeitsweise Erledige mehr mit Trello Nutze unkomplizierte Integrationen, Automatisierung und Spiegelung deiner Aufgaben an mehreren Standorten für eine individuelle Organisation. Integrationen Binde Apps, mit denen du bereits arbeitest, in deinen Trello-Workflow ein, oder füge ein Power-Up hinzu, um eine bestimmte Aufgabe zu erfüllen. Integrationen durchsuchen Automatisierung Jedes Trello-Board bietet eine integrierte Automatisierung ohne Code. Konzentriere dich auf die wirklich wichtige Arbeit, während die Roboter den Rest erledigen. Lerne die Automatisierung kennen Kartenspiegelung Zeige all deine Aufgaben von verschiedenen Boards an einer zentralen Stelle an. Du kannst Karten spiegeln, um deine Aufgaben dort im Blick zu behalten, wo du gerade arbeitest. Tarife vergleichen [Trello ist] großartig, um komplexe Prozesse zu vereinfachen. Als Manager kann ich [Prozesse] in mundgerechte Stücke für mein Team zerlegen und diese dann delegieren, aber immer noch den Überblick behalten. Joey Rosenberg Global Leadership Director bei Women Who Code Story lesen 75 % der Organisationen geben an, dass Trello innerhalb von 30 Tagen einen Mehrwert für ihr Unternehmen liefert. Trello TechValidate-Umfrage Egal, ob im Büro, von zu Hause aus oder vor Ort mit einem Kunden gearbeitet wird: Kontext und Informationen können über Trello geteilt werden. Sumeet Moghe Produktmanager bei ThoughtWorks Story lesen 81 % der Kunden entschieden sich für Trello wegen seiner Benutzerfreundlichkeit. Trello TechValidate-Umfrage Wir verwendeten Trello, um mehr Klarheit bezüglich der Schritte, Anforderungen und Verfahren zu schaffen. Das war außerordentlich, wenn man mit Teams kommunizierte, die sich hinsichtlich Kultur und Sprache deutlich unterscheiden. Jefferson Scomacao Entwicklungsmanager bei IKEA/PTC Story lesen 74 % der Kunden sagen, dass Trello die Kommunikation mit ihren Kollegen und Teams verbessert hat. Trello TechValidate-Umfrage Tritt einer Community aus Millionen von Benutzern weltweit bei, die für höhere Produktivität bereits auf Trello vertraut. Tritt einer Community aus Millionen von Benutzern weltweit bei, die für höhere Produktivität bereits auf Trello vertraut. Starte noch heute mit Trello durch Jetzt registrieren – es ist kostenlos! Durch Eingabe meiner E-Mail-Adresse erkenne ich die Datenschutzrichtlinie von Atlassian an. Anmelden Informationen zu Trello Was hinter den Boards steckt. Stellenangebote Informiere dich über offene Stellen im Trello-Team. Apps Lade die Trello-App auf deinen Computer oder dein Mobilgerät herunter. Kontakt Hast du eine Frage? Kontaktiere uns – wir helfen dir gern! Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Datenschutzrichtlinie Nutzungsbedingungen Copyright © 2023 Atlassian | 2026-01-13T09:29:41 |
https://git-scm.com/book/pt-br/v2/Fundamentos-de-Git-Trabalhando-de-Forma-Remota | Git - Trabalhando de Forma Remota About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Resumo A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.5 Fundamentos de Git - Trabalhando de Forma Remota Trabalhando de Forma Remota Para colaborar com qualquer projeto Git, você precisará saber como gerenciar seus repositórios remotos. Repositórios remotos são versões de seu repositório hospedado na Internet ou em uma rede qualquer. Você pode ter vários deles, cada um dos quais geralmente é ou somente leitura ou leitura/escrita. Colaborar com outras pessoas envolve o gerenciamento destes repositórios remotos, fazer pushing (atualizar) e pulling (obter) de dados para e deles quando você precisar compartilhar seu trabalho. Gerenciar repositórios remotos inclui saber como adicioná-los remotamente, remover aqueles que não são mais válidos, gerenciar vários branches (ramos) e definí-los como rastreados ou não e muito mais. Nesta seção, abordaremos algumas destas habilidades de gereciamento remoto. Exibindo seus repositórios remotos Para ver quais servidores remotos você configurou, você pode executar o comando git remote . Ele lista os nomes abreviados de cada repositório remoto manejado que você especificou. Se você clonou seu repositório, você deve pelo menos ver origin (origem) – que é o nome padrão dado pelo Git ao servidor que você clonou: $ git clone https://github.com/schacon/ticgit Cloning into 'ticgit'... remote: Reusing existing pack: 1857, done. remote: Total 1857 (delta 0), reused 0 (delta 0) Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done. Resolving deltas: 100% (772/772), done. Checking connectivity... done. $ cd ticgit $ git remote origin Você também pode especificar -v , que mostra as URLs que o Git tem armazenado pelo nome abreviado a ser usado para ler ou gravar naquele repositório remoto: $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) Se você tem mais de um repositório remoto, o comando lista todos eles. Por exemplo, um repositório com diversos repositórios remotos para trabalhar com vários colaboradores pode ser algo parecido com isto: $ cd grit $ git remote -v bakkdoor https://github.com/bakkdoor/grit (fetch) bakkdoor https://github.com/bakkdoor/grit (push) cho45 https://github.com/cho45/grit (fetch) cho45 https://github.com/cho45/grit (push) defunkt https://github.com/defunkt/grit (fetch) defunkt https://github.com/defunkt/grit (push) koke git://github.com/koke/grit.git (fetch) koke git://github.com/koke/grit.git (push) origin git@github.com:mojombo/grit.git (fetch) origin git@github.com:mojombo/grit.git (push) Isto significa que nós podemos obter( pull ) contribuições de qualquer um desses usuários muito facilmente. Nós podemos, adicionalmente, ter a permissão de atualizar( push ) um ou mais destes, embora não possamos dizer isso nesse caso. Note que estes repositórios remotos usam uma variedade de protocolos e nós falaremos mais sobre isso em Getting Git on a Server . Adicionando Repositórios Remotos Nós mencionamos e demos algumas demonstrações de como o comando clone implicitamente adiciona a origem( origin ) remota para você. Aqui está como adicionar um novo repositório remoto explicitamente. Para adicionar um novo repositório Git remoto como um nome curto que você pode referenciar facilmente, execute git remote add <shortname> <url> : $ git remote origin $ git remote add pb https://github.com/paulboone/ticgit $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) pb https://github.com/paulboone/ticgit (fetch) pb https://github.com/paulboone/ticgit (push) Agora você pode usar a string pb na linha de comando no lugar de uma URL completa. Por exemplo, se você quiser buscar toda a informação que Paul tem, mas você ainda não tem em seu repositório, você pode executar git fetch pb : $ git fetch pb remote: Counting objects: 43, done. remote: Compressing objects: 100% (36/36), done. remote: Total 43 (delta 10), reused 31 (delta 5) Unpacking objects: 100% (43/43), done. From https://github.com/paulboone/ticgit * [new branch] master -> pb/master * [new branch] ticgit -> pb/ticgit O master branch (ramo mestre) do Paul agora está acessível localmente como pb/master – você pode fundí-lo( merge ) dentro de uma de suas ramificações( branches ) ou você pode checar fora da ramificação local se você quiser inspecioná-lo. (Nós abordaremos o que são ramificações( branches ) e como usá-las mais detalhadamente em [ch03-git-branching] . ) Buscando e Obtendo de seus Repositórios Remotos Como você viu, para obter dados de seus projetos remotos, você pode executar: $ git fetch [remote-name] O comando vai até aquele projeto remoto e extrai todos os dados daquele projeto que você ainda não tem. Depois que você faz isso, você deve ter como referência todos as ramificações( branches ) daquele repositório remoto, que você pode mesclar( merge ) com o atual ou inspecionar a qualquer momento. Se você clonar um repositório, o comando automaticamente adiciona àquele repositório remoto com o nome origin . Então, git fetch origin busca qualquer novo trabalho que tenha sido enviado para aquele servidor desde que você o clonou ou fez a última busca( fetch ). É importante notar que o comando git fetch só baixa os dados para o seu repositório local - ele não é automaticamente mesclado( merge ) com nenhum trabalho seu ou modificação que você esteja trabalhando atualmente. Você deve mesclá-los manualmente dentro de seu trabalho quando você estiver pronto. Se o branch atual é configurando para rastrear um branch remoto (veja a próxima seção e [ch03-git-branching] para mais informação), você pode usar o comando git pull para buscar( fetch ) e então mesclar( merge ) automaticamente aquele branch remoto dentro do seu branch atual. Este pode ser um fluxo de trabalho mais fácil e mais confortável para você, e por padrão, o comando git clone automaticamente configura a sua master branch local para rastrear a master branch remota ou qualquer que seja o nome do branch padrão no servidor de onde você o clonou. Executar git pull comumente busca os dados do servidor de onde você originalmente clonou e automaticamente tenta mesclá-lo dentro do código que você está atualmente trabalhando. Pushing to Your Remotes Quando você tem seu projeto em um ponto que deseja compartilhar, é necessário enviá-lo para o servidor remoto. O comando para isso é simples: git push [remote-name] [branch-name] . Se você quiser enviar sua ramificacão (branch) master para o servidor origin (novamente, a clonagem geralmente configura ambos os nomes para você automaticamente), então você pode executar isso para enviar quaisquer commits feitos para o servidor: $ git push origin master Este comando funciona apenas se você clonou de um servidor ao qual você tem acesso de escrita (write-access) e se ninguém mais utilizou o comando push nesse meio-tempo. Se você e outra pessoa clonarem o repositório ao mesmo tempo e ela utilizar o comando push e, em seguida, você tentar utilizar, seu envio será rejeitado. Primeiro você terá que atualizar localmente, incorporando o trabalho dela ao seu, só assim você poderá utilizar o comando push. Veja [ch03-git-branching] para informações mais detalhadas sobre como enviar para servidores remotos. Inspecionando o Servidor Remoto Se você quiser ver mais informações sobre um servidor remoto em particular, você pode usar o comando git remote show [nome-remoto] . Ao executar este comando com um nome abreviado específico, como origin , obterá algo assim: $ git remote show origin * remote origin Fetch URL: https://github.com/schacon/ticgit Push URL: https://github.com/schacon/ticgit HEAD branch: master Remote branches: master tracked dev-branch tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) Ele lista a URL para o repositório remoto, bem como as informações de rastreamento do branch. O comando, de forma útil, comunica que se você estiver no branch master e executar git pull , ele irá mesclar (merge) automaticamente no branch master do servidor após buscar (fetch) todas as referências remotas. Ele também lista todas as referências remotas recebidas. Esse é um exemplo simples que você provavelmente encontrará. Quando você usa o Git mais intensamente, no entanto, pode ver muito mais informações com git remote show : $ git remote show origin * remote origin URL: https://github.com/my-org/complex-project Fetch URL: https://github.com/my-org/complex-project Push URL: https://github.com/my-org/complex-project HEAD branch: master Remote branches: master tracked dev-branch tracked markdown-strip tracked issue-43 new (next fetch will store in remotes/origin) issue-45 new (next fetch will store in remotes/origin) refs/remotes/origin/issue-11 stale (use 'git remote prune' to remove) Local branches configured for 'git pull': dev-branch merges with remote dev-branch master merges with remote master Local refs configured for 'git push': dev-branch pushes to dev-branch (up to date) markdown-strip pushes to markdown-strip (up to date) master pushes to master (up to date) Este comando mostra para qual ramificação (branch) é enviada automaticamente quando você executa git push enquanto em certas ramificações. Ele também mostra quais branches remotos do servidor você ainda não tem, quais você tem que foram removidos do servidor e várias branches locais que são capazes de se fundir automaticamente com seu branch de rastreamento remoto quando você executa git pull . Removendo e Renomeando Remotes Você pode utilizar o git remote rename para alterar o nome curto de servidores remotos. Por exemplo, se você deseja renomear pb para` paul`, você pode fazer isso com git remote rename : $ git remote rename pb paul $ git remote origin paul Vale a pena mencionar que isso muda todos os nomes de ramificações de rastreamento remoto também. O que costumava ser referenciado em pb/master agora está em paul/master . Se você quiser remover um servidor remoto por algum motivo - e você anteriormente moveu o servidor ou não está mais usando um em particular, ou talvez um contribuidor não esteja mais contribuindo - você pode usar git remote remove ou git remote rm : $ git remote remove paul $ git remote origin prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://git-scm.com/book/pt-br/v2/Branches-no-Git-Fluxo-de-Branches | Git - Fluxo de Branches About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Resumo A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 3.4 Branches no Git - Fluxo de Branches Fluxo de Branches Agora que você tem o básico sobre branches e merges, o que você pode ou deve fazer com eles? Nesta seção, cobriremos alguns fluxos de trabalho comuns que o branch torna possível, para que você possa decidir se deseja incorporá-los em seu próprio ciclo de desenvolvimento. Branches de longa duração Como o Git usa uma mesclagem simples de três vias, mesclar de um branch para outro várias vezes durante um longo período é geralmente fácil de fazer. Isso significa que você pode ter vários branches que estão sempre abertos e que você usa para diferentes estágios do seu ciclo de desenvolvimento; você pode mesclar regularmente alguns deles com outros. Muitos desenvolvedores Git têm um fluxo de trabalho que adota essa abordagem, como ter apenas código totalmente estável em seu branch master - possivelmente apenas código que foi ou será lançado. Eles têm outro branch paralelo chamado developers ou next , a partir do qual trabalham ou usam para testar a estabilidade - não é necessáriamente sempre estável, mas sempre que chega a um estado estável, pode ser mesclado com o master . É usado para puxar branches de tópico (de curta duração, como seu anterior iss53 ) quando eles estão prontos, para garantir que eles passem em todos os testes e não introduzam bugs. Na realidade, estamos falando sobre indicadores que aumentam a linha de commits que você está fazendo. Os branches estáveis estão mais abaixo na linha em seu histórico de commit, e os branches mais avançados estão mais adiante no histórico. Figure 26. Uma visão linear de branches de estabilidade progressiva Geralmente é mais fácil pensar neles como silos de trabalho, onde conjuntos de commits passam para um silo mais estável quando são totalmente testados. Figure 27. A visão de “silo” de branches de estabilidade progressiva Você pode continuar fazendo isso por vários níveis de estabilidade. Alguns projetos maiores também têm um ramo proposto ou pu (proposed updates) que tem branches integrados que podem não estar prontos para ir para o branch next ou master . A ideia é que seus ramos estejam em vários níveis de estabilidade; quando eles atingem um nível mais estável, eles são mesclados no ramo acima deles. Novamente, não é necessário ter vários branches de longa duração, mas geralmente é útil, especialmente quando você está lidando com projetos muito grandes ou complexos. Branches por tópicos Branches de tópicos, no entanto, são úteis em projetos de qualquer tamanho. Um branch de tópico é um branch de curta duração que você cria e usa para um único recurso específico ou trabalho relacionado. Isso é algo que você provavelmente nunca fez com um VCS antes porque geralmente é muito difícil para criar e mesclar branches. Mas no Git é comum criar, trabalhar, mesclar e excluir branches várias vezes ao dia. Você viu isso na última seção com os branches iss53 e hotfix que você criou. Você fez alguns commits neles e os deletou diretamente após fundi-los em seu branch principal. Esta técnica permite que você mude de contexto de forma rápida e completa - porque seu trabalho é separado em silos onde todas as mudanças naquele branch têm a ver com aquele tópico, é mais fácil ver o que aconteceu durante a revisão de código. Você pode manter as alterações lá por minutos, dias ou meses e mesclá-las quando estiverem prontas, independentemente da ordem em que foram criadas ou trabalhadas. Considere um exemplo de como fazer algum trabalho (no master ), ramificando para um problema ( iss91 ), trabalhando nisso um pouco, ramificando o segundo branch para tentar outra maneira de lidar com a mesma coisa ( iss91v2 ), voltando ao seu branch master e trabalhando lá por um tempo, e então ramificando para fazer algum trabalho que você não tem certeza se é uma boa ideia (branch dumbidea ). Seu histórico de commits será parecido com isto: Figure 28. Branches de tópico múltiplos Agora, digamos que você decida que prefere a segunda solução para o seu problema ( iss91v2 ); e você mostrou o branch dumbidea para seus colegas de trabalho, e acabou sendo um gênio. Você pode descartar o branch iss91 original (perdendo commits C5 e C6 ) e mesclar os outros dois. Seu histórico será assim: Figure 29. Histórico após mesclar dumbidea and iss91v2 Iremos entrar em mais detalhes sobre os vários fluxos de trabalho possíveis para seu projeto Git em [ch05-distributed-git] , portanto, antes de decidir qual esquema de ramificação seu próximo projeto usará, certifique-se de ler esse capítulo. É importante lembrar quando você estiver fazendo tudo isso que esses branches são completamente locais. Quando você está ramificando e mesclando, tudo está sendo feito apenas em seu repositório Git - nenhuma comunicação com o servidor está acontecendo. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://www.atlassian.com/ja/enterprise/success/advisory-services | 戦略的コンサルタント サービス | Atlassian Close あなたの言語 でこのページを表示しますか？ すべての言語 言語を選択する 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 営業窓口 概要 成功 リソース その他 + 表示を減らす - 営業窓口 Back 営業窓口 エンタープライズ サービス Advisory services Advisory Service あらゆる可能性を引き出す あらゆる変革の野望を現実のものにします。戦略的ガイダンスと最適化されたソリューションで、アトラシアンへの投資を最大化します。 お問い合わせ アトラシアンのアドバイザリー・サービスについて 今すぐ見る 変化のスピードに容易に適応 動的な世界では、今日の課題を乗り越えるだけでは十分ではありません。アトラシアンは、変革のために強力で拡張可能な基盤を構築するお手伝いをします。この構築により、現在の場所から必要な場所へとお客様は自信を持って移行できます。 成果の最大化と リスクの最小化 自信を持って持続的な成功を収め、 技術的負債 を回避します。アトラシアンは、お客様が思いもつかなかった重要な要素や強化点を発見し、課題への取り組みをサポートして、明確な道筋を確保します。 成功の加速 包括的なソリューション設計の利点をご覧ください。ソリューション パートナーと協力して、デプロイと導入を成功に導きます。 パフォーマンスの改善 さらなる収益機会をつかみ、コストを削減します。価値創造までの時間を短縮し、イノベーションを促進するために、チームのプラクティス、ワークフローおよびツールチェーンを強化することで、製品構成の枠を超えます。 カスタマイズされたエキスパート チーム アトラシアンは世界最大規模の組織の変革をサポートしてきました。お客様も同じことができます。私たちのチームと一緒に、より良い決断を下しましょう。 ストラテジック エンゲージメント マネージャー (SEM) 戦略的計画を策定し、より良い成果を達成するために計画の実行を指揮します。 エンタープライズ ソリューション ストラテジスト (ESS) DevOps、アジャイル、ITSM、作業管理、クラウドに合わせたベスト プラクティスを提供します。 エンタープライズ テクニカル アーキテクト (ETA) 最適なソリューション設計、デプロイの成功、導入のための技術的ガイダンスを提供します。 オプションを見る サブスクリプション プラン 変革の取り組みの段階に合わせて、結果重視のオプションをご覧ください。 詳細を見る サービス カタログ アトラシアンのプラットフォームやドメイン サービスの詳細を確認し、強固な基盤を迅速に確立してチーム プラクティスを最適化しましょう。 詳細を見る お問い合わせ ご興味をお持ちの方は、アトラシアンの Advisory Service チームがお手伝いします。 お問い合わせ 会社名 アトラシアンで働く イベント ブログ 投資家向け アトラシアン基金 プレスキット お問い合わせ 製品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket すべての製品を見る リソース 技術サポート 購入とライセンス アトラシアン コミュニティ ナレッジ ベース Marketplace アカウント管理 サポートを依頼する 学ぶ パートナー トレーニングと認定 ドキュメント 開発者向けリソース エンタープライズ サービス 全リソースを見る Copyright © 2025 Atlassian プライバシーポリシー 利用規約 サイト管理者情報 言語の選択 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://www.linkedin.com/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fcoachhub&fromSignIn=true&trk=top-card_top-card-secondary-button-top-card-secondary-cta | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:41 |
https://support.smartbear.com/reflect/docs/en/api/tests-api.html#get-execution-status-2110494 | Tests API | Reflect Documentation Skip to main content Support Toggle navigation Toggle navigation Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup How to Track Usage Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions in Reflect Mobile Working with CI/CD Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Default Headers Email / SMS Testing Private Environments Local Testing Automating Manual Tests Manage Tests View Test Run Editing / Re-Recording Folders Suites API Request Signing Suites API Tests API Integrations Continuous Integration (CI/CD) Email Notifications Slack GitHub Issue Trackers Test Case Management Release Notes Reflect Tunnel print Toggle navigation Prev Next Reflect Documentation Developer API Tests API Tests API Execute tests and get the status of individual test runs. List all tests Returns a list of test descriptions containing the test’s id, name, created timestamp and folders. REQUEST GET https://api.reflect.run/v1/tests RESPONSE { "tests": [ { "id": 3072323, "name": "Registration Flow", "created": 1570546969108, "folders": [ "regression-tests" ] } ] } RESPONSE FIELDS tests object: A list of test descriptions, including the test's id, name and folders. Run a test Immediately schedules a test. The browser field allows you to specify the browser to run the test with. Supported values are: Chrome , Edge , Firefox , and Safari - if no value is specified Chrome is used. Note Your account must have access to the requested browser - requesting an unsupported browser will return a 400 error code. Reflect identifies certain properties of the execution as “reserved”. These reserved fields can be overridden with values provided by the API request: hostnames : Allows you to specify a replacement hostname value for a given target hostname. You can also optionally specify a new port by including it in the replacement (see below for an example). If your override specifies a port, note the following behavior: If original includes a port value, it will only be applied on URLs of the test that also use that same port. For example, an original value of example.com:1234 would have no effect on https://example.com or https://example.com:5678. If original does not include a port value, it will match every URL of the test that uses the same hostname, regardless of port. For example, an original value of example.com would match both https://example.com and https://example.com:1234. If a port was specified in the URL of the test, it will be preserved unless a new value is specified in replacement or original included the port and replacement did not - in that case no port would be included in the resulting URL. agent : Allows you to select a specific Tunnel to run the test through by specifying the agent’s name. parameters : Allows you to specify a URL parameter key/value pair that will be included (or overwritten) on the test’s initial URL. cookies : Allows you to specify cookies that will be set when loading the test’s initial URL. A cookie consists of the following fields: name (required string): The name of the cookie to be set. value (required string): The cookie’s value. domain (optional string): Host to which the cookie will be sent. Defaults to the host of the test’s initial URL. expires (optional number): Epoch timestamp (in milliseconds) indicating when the cookie should be deleted. If unspecified, the cookie becomes a session cookie. httpOnly (optional boolean): Indicates the cookie should be inaccessible to JavaScript on the page and only sent to the server. maxAge (optional number): Number of milliseconds until the cookie expires. If both expires and maxAge are set, maxAge has precedence. path (optional string): A URL path that must exist in a request URL in order to include the cookie in a request. secure (optional boolean): Indicates that the cookie should only be sent to the server when a request is made with https: . headers : Allows you to specify headers that will be sent when loading the test’s initial URL. name (required string): The name of the header. value (required string): The header value. persist (optional boolean): Specifies whether this header should only be set in the initial request or for every subsequent HTTP request (ex: when overriding the Accept-Language header). If set to true , the Authorization header is only set for requests that match the hostname of the test’s original URL. Defaults to false . localStorage and sessionStorage : Allows you to specify local and session storage values to be set on the test’s initial URL. The variables field allows you to specify a definition for a variable used in the test. REQUEST POST https://api.reflect.run/v1/tests/<test-id>/executions { "browser": "Chrome", "overrides": { "agent": { "name": "agent-name" }, "hostnames": [{ "original": "prod.myapp.com", "replacement": "staging.myapp.com:1234" }], "parameters": [{ "key": "token", "value": "abcdef" }], "cookies": [{ "name": "my-favorite-cookie", "value": "chocolate-chip", "domain": "myapp.com", "expires": 123456789, "httpOnly": false, "maxAge": 123, "path": "/", "secure": true }], "headers": [{ "name": "X-Custom-Header", "value": "custom-value" }], "localStorage": [{ "key": "my-local-key", "value": "local-value" }], "sessionStorage": [{ "key": "my-session-key", "value": "session-value" }] }, "variables": { "username1": "user+${alpha(8)}@example.com", "password": "acompletelyunguessablepassword" }, "emailFailures": true } REQUEST FIELDS overrides optional object: Overrides to apply to properties of the test being executed. agent (object, optional) name (string, required) — The name of the Tunnel/Agent to use for this execution. variables optional object: Collection of ('name', 'definition') variable overrides to apply to this scheduled execution. emailFailures optiona boolean: Controls whether email notifications should be sent for a failed test run. The default is true. RESPONSE { "executionId": 8939 } RESPONSE FIELDS executionId number: An identifier for the scheduled execution created by the request. Get execution status Returns a list of test result objects. The test result object includes the test’s id and a status field describing whether the test is “queued”, “running”, “succeeded”, or “failed”. Additionally, it contains a run object describing the properties of the test run such as its starting and ending time, and its video URL. REQUEST GET https://api.reflect.run/v1/executions/<execution-id> RESPONSE { "executionId": 17671, "browser": "Edge", "tests": [ { "testId": 1690, "status": "succeeded", "run": { "runId": 690, "status": "passed", "variables": {}, "startTime": 1654632014295, "endTime": 1654632027297, "runTime": 13002, "videoUrl": "https://reflect-videos.s3.amazonaws.com/690_89f4.mp4" } } ] } RESPONSE FIELDS executionId number: An identifier for the scheduled execution. browser string: The browser that the tests in the scheduled execution are configured to run on. tests object: List of test results, including the testId and status. tests.testId number: An identifier for the test. tests.status string: One of: queued, running, succeeded, or failed. Summarizes the outcome of the test instance from its runs. tests.run object: The test run from this execution. tests.run.runId number: An identifier for the test run. tests.run.status string: The outcome of the test run. Either passed or failed. tests.run.variables object: The variables that were used or created by the test run. tests.run.startTime number: Timestamp of when the test run started. tests.run.endTime number: Timestamp of when the test run stopped. tests.run.runTime number: Total time that the test run spent running (endTime - startTime). tests.run.videoUrl string: The URL of a video recording of the test run. In this section : Tests API List all tests Run a test Get execution status Search results No results found Prev Next © 2025 Publication date : Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:41 |
https://l.facebook.com/l.php?u=https%3A%2F%2F10web.io%2Fblog%2Fvps-hosting-vs-dedicated-hosting%2F&h=AT1sJw2vZinqAXwacR93PSOBP7NtWLdr6MrpT_1nkVEQGHtopWAi9e_o9W-A4Z6TW3hB11MCVSbhsTYN6IPTXfjVrO1gR91lxSOZb7C0drvasiFJVaPXnxAGSFVeyorpmRAwPbGe1D7VLNDg | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:41 |
https://git-scm.com/book/it/v2/Git-Basics-Working-with-Remotes | Git - Working with Remotes About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Per Iniziare 1.1 Il Controllo di Versione 1.2 Una Breve Storia di Git 1.3 Cos’é Git? 1.4 La riga di comando 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Chiedere aiuto 1.8 Sommario 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Sommario 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendice A: Git in altri contesti A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Riassunto A2. Appendice B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendice C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.5 Git Basics - Working with Remotes Working with Remotes To be able to collaborate on any Git project, you need to know how to manage your remote repositories. Remote repositories are versions of your project that are hosted on the Internet or network somewhere. You can have several of them, each of which generally is either read-only or read/write for you. Collaborating with others involves managing these remote repositories and pushing and pulling data to and from them when you need to share work. Managing remote repositories includes knowing how to add remote repositories, remove remotes that are no longer valid, manage various remote branches and define them as being tracked or not, and more. In this section, we’ll cover some of these remote-management skills. Showing Your Remotes To see which remote servers you have configured, you can run the git remote command. It lists the shortnames of each remote handle you’ve specified. If you’ve cloned your repository, you should at least see origin – that is the default name Git gives to the server you cloned from: $ git clone https://github.com/schacon/ticgit Cloning into 'ticgit'... remote: Reusing existing pack: 1857, done. remote: Total 1857 (delta 0), reused 0 (delta 0) Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done. Resolving deltas: 100% (772/772), done. Checking connectivity... done. $ cd ticgit $ git remote origin You can also specify -v , which shows you the URLs that Git has stored for the shortname to be used when reading and writing to that remote: $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) If you have more than one remote, the command lists them all. For example, a repository with multiple remotes for working with several collaborators might look something like this. $ cd grit $ git remote -v bakkdoor https://github.com/bakkdoor/grit (fetch) bakkdoor https://github.com/bakkdoor/grit (push) cho45 https://github.com/cho45/grit (fetch) cho45 https://github.com/cho45/grit (push) defunkt https://github.com/defunkt/grit (fetch) defunkt https://github.com/defunkt/grit (push) koke git://github.com/koke/grit.git (fetch) koke git://github.com/koke/grit.git (push) origin git@github.com:mojombo/grit.git (fetch) origin git@github.com:mojombo/grit.git (push) This means we can pull contributions from any of these users pretty easily. We may additionally have permission to push to one or more of these, though we can’t tell that here. Notice that these remotes use a variety of protocols; we’ll cover more about this in Getting Git on a Server . Adding Remote Repositories I’ve mentioned and given some demonstrations of adding remote repositories in previous sections, but here is how to do it explicitly. To add a new remote Git repository as a shortname you can reference easily, run git remote add [shortname] [url] : $ git remote origin $ git remote add pb https://github.com/paulboone/ticgit $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) pb https://github.com/paulboone/ticgit (fetch) pb https://github.com/paulboone/ticgit (push) Now you can use the string pb on the command line in lieu of the whole URL. For example, if you want to fetch all the information that Paul has but that you don’t yet have in your repository, you can run git fetch pb : $ git fetch pb remote: Counting objects: 43, done. remote: Compressing objects: 100% (36/36), done. remote: Total 43 (delta 10), reused 31 (delta 5) Unpacking objects: 100% (43/43), done. From https://github.com/paulboone/ticgit * [new branch] master -> pb/master * [new branch] ticgit -> pb/ticgit Paul’s master branch is now accessible locally as pb/master – you can merge it into one of your branches, or you can check out a local branch at that point if you want to inspect it. (We’ll go over what branches are and how to use them in much more detail in [ch03-git-branching] .) Fetching and Pulling from Your Remotes As you just saw, to get data from your remote projects, you can run: $ git fetch [remote-name] The command goes out to that remote project and pulls down all the data from that remote project that you don’t have yet. After you do this, you should have references to all the branches from that remote, which you can merge in or inspect at any time. If you clone a repository, the command automatically adds that remote repository under the name “origin”. So, git fetch origin fetches any new work that has been pushed to that server since you cloned (or last fetched from) it. It’s important to note that the git fetch command pulls the data to your local repository – it doesn’t automatically merge it with any of your work or modify what you’re currently working on. You have to merge it manually into your work when you’re ready. If you have a branch set up to track a remote branch (see the next section and [ch03-git-branching] for more information), you can use the git pull command to automatically fetch and then merge a remote branch into your current branch. This may be an easier or more comfortable workflow for you; and by default, the git clone command automatically sets up your local master branch to track the remote master branch (or whatever the default branch is called) on the server you cloned from. Running git pull generally fetches data from the server you originally cloned from and automatically tries to merge it into the code you’re currently working on. Pushing to Your Remotes When you have your project at a point that you want to share, you have to push it upstream. The command for this is simple: git push [remote-name] [branch-name] . If you want to push your master branch to your origin server (again, cloning generally sets up both of those names for you automatically), then you can run this to push any commits you’ve done back up to the server: $ git push origin master This command works only if you cloned from a server to which you have write access and if nobody has pushed in the meantime. If you and someone else clone at the same time and they push upstream and then you push upstream, your push will rightly be rejected. You’ll have to pull down their work first and incorporate it into yours before you’ll be allowed to push. See [ch03-git-branching] for more detailed information on how to push to remote servers. Inspecting a Remote If you want to see more information about a particular remote, you can use the git remote show [remote-name] command. If you run this command with a particular shortname, such as origin , you get something like this: $ git remote show origin * remote origin Fetch URL: https://github.com/schacon/ticgit Push URL: https://github.com/schacon/ticgit HEAD branch: master Remote branches: master tracked dev-branch tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) It lists the URL for the remote repository as well as the tracking branch information. The command helpfully tells you that if you’re on the master branch and you run git pull , it will automatically merge in the master branch on the remote after it fetches all the remote references. It also lists all the remote references it has pulled down. That is a simple example you’re likely to encounter. When you’re using Git more heavily, however, you may see much more information from git remote show : $ git remote show origin * remote origin URL: https://github.com/my-org/complex-project Fetch URL: https://github.com/my-org/complex-project Push URL: https://github.com/my-org/complex-project HEAD branch: master Remote branches: master tracked dev-branch tracked markdown-strip tracked issue-43 new (next fetch will store in remotes/origin) issue-45 new (next fetch will store in remotes/origin) refs/remotes/origin/issue-11 stale (use 'git remote prune' to remove) Local branches configured for 'git pull': dev-branch merges with remote dev-branch master merges with remote master Local refs configured for 'git push': dev-branch pushes to dev-branch (up to date) markdown-strip pushes to markdown-strip (up to date) master pushes to master (up to date) This command shows which branch is automatically pushed to when you run git push while on certain branches. It also shows you which remote branches on the server you don’t yet have, which remote branches you have that have been removed from the server, and multiple branches that are automatically merged when you run git pull . Removing and Renaming Remotes If you want to rename a reference you can run git remote rename to change a remote’s shortname. For instance, if you want to rename pb to paul , you can do so with git remote rename : $ git remote rename pb paul $ git remote origin paul It’s worth mentioning that this changes your remote branch names, too. What used to be referenced at pb/master is now at paul/master . If you want to remove a remote for some reason – you’ve moved the server or are no longer using a particular mirror, or perhaps a contributor isn’t contributing anymore – you can use git remote rm : $ git remote rm paul $ git remote origin prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://www.linkedin.com/products/coachhub--the-digital-coaching-platform?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | CoachHub - The digital coaching platform | LinkedIn Skip to main content LinkedIn CoachHub - The digital coaching platform in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in CoachHub - The digital coaching platform AI-Powered Coaching Software by CoachHub - The digital coaching platform See who's skilled in this Add as skill Learn more Report this product About CoachHub is the global leader in digital coaching. We enable organizations to deliver personalized, scalable coaching programs that drive measurable business impact across the workforce. Coaching Solutions Designed for Scale ✔️CoachHub Individual: Support long-term growth by giving employees access to world-class business coaches. ✔️CoachHub Executive™: Help senior leaders turn complexity into clarity and vision into results. ✔️CoachHub Collective: Build stronger teams through expert-led group coaching that accelerates collaboration and problem-solving. ✔️AIMY™: Our pioneering AI coach makes coaching scalable, measurable and accessible across the organization. The Business Impact ✔️Companies that partner with CoachHub see: ✔️Higher employee engagement and retention ✔️Measurable improvements in productivity and performance ✔️Stronger leadership pipelines and employer brand Media Products media viewer No more previous content Transform People and Organizations Coaching can be life-changing. But don't just take it from us – hear it first-hand from some of our customers. What if you could unlock meaningful experiences at work, empower employees to embrace change and bring out the best in your leaders? Transform your teams through digital coaching with CoachHub. Get started today at coachhub.com. Building Future-Ready Leaders Discover how Schneider Electric revolutionized its leadership development strategy through a global digital coaching program in partnership with CoachHub. In this powerful case study, you'll hear firsthand from Schneider Electric leaders in North America as they share the impact of scaling personalized coaching to over 6,000 managers. #LeadershipDevelopment #DigitalCoaching #CoachHub #SchneiderElectric #HRInnovation #FutureOfWork #CaseStudy AIMY™: the AI Coach for the global workforce Provide employees across all career levels with a personalized, goal-oriented AI coach. Experience the power of our coaching programs Leverage our science-backed coaching framework to upskill your workforce and transform your organization. Make Collective Intelligence Your Superpower Build a culture of collaboration to multiply your workforce potential with CoachHub Collective No more next content Featured customers of CoachHub - The digital coaching platform The Coca-Cola Company Food and Beverage Services 8,635,710 followers Generali Insurance 570,803 followers Atlas Copco Group Machinery Manufacturing 192,115 followers Booking.com Software Development 1,101,962 followers Virgin Atlantic Airlines and Aviation 432,418 followers BNP Paribas Banking 1,870,442 followers Schneider Electric Automation Machinery Manufacturing 5,289,556 followers ENGIE Renewable Energy Power Generation 1,070,536 followers Danone Food and Beverage Manufacturing 3,767,250 followers Show more Show less Similar products LinkedIn Learning AI-powered Coaching LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software LinkedIn Interview Prep AI LinkedIn Interview Prep AI AI-Powered Coaching Software AI Resume Builder AI Resume Builder AI-Powered Coaching Software MOBILITY MOBILITY AI-Powered Coaching Software Exponent Practice Exponent Practice AI-Powered Coaching Software Yoodli AI Roleplays Yoodli AI Roleplays AI-Powered Coaching Software Sign in to see more Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:41 |
https://docs.google.com/forms/d/e/1FAIpQLSd-TziNhzY2PvwQGpM5WbcB7oikW2l_6xYMCmn625B3tNQ7Dg/viewform?usp=dialog | Everything Open 2026 - Volunteer Expressions of Interest Everything Open 2026 - Volunteer Expressions of Interest Applications to volunteer at Everything Open 2026 aren't open right now. 이 콘텐츠는 Google이 만들거나 승인하지 않았습니다. - 서비스 약관 - 개인정보처리방침 양식이 의심스러운가요? 보고서 설문지 | 2026-01-13T09:29:41 |
https://www.linkedin.com/posts/verified-first_hrcalendar-humanresources-2026planning-activity-7414704371352915968-FF65#main-content | #hrcalendar #humanresources #2026planning #hrcompliance | Verified First Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Register now Verified First’s Post Verified First 7,992 followers 5d Report this post Is your HR team's 2026 calendar still living in three different spreadsheets? Now that the holidays are over, it's the perfect time to get organized for the new year. Stop wasting hours searching through old files for tax deadlines and compliance forms. Your team needs a single reliable resource for 2026. Verified First’s 2026 HR Compliance Calendar and Checklist is your reliable, actionable guide to streamline administrative priorities. Download your copy now! https://lnkd.in/gkiyybdj #HRcalendar #HumanResources #2026planning #HRcompliance 10 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 7,992 followers View Profile Connect Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T09:29:41 |
https://lever.co/solution-add-ons-overview/ | Solution Add-ons Overview - Lever Sales: (888) 885.5299 Sign In Support Solutions AI Companions AI Interview Companion AI Screening Companion Solutions Recruitment Marketing High-Volume Hiring Diversity & Inclusion Hiring Recruitment Automation Recruitment Analytics Recruitment Communication Career Site Builder Solution Add Ons View All Check Out Our Product Guide See Product Guide Resources Learn Blog Hiring & Recruiting Resources Connect Events & Webinars 2025 Benchmarks Report Get the Report Company Company Why Lever What Customers Say Partner Integrations Careers Join our Team Request Demo Pricing Solutions For You Packaged solutions for your most pressing needs. Automate redundant tasks and streamline processes, attract your best talent with personalized outreach, and get the best access to your recruiting and hiring data with one of Lever’s Solution Add-ons. Get a Demo 5,000+ Customers Worldwide Trust Lever --> Product Tour: Tour Our Award-Winning Recruitment Software Whether you have 100 reqs or just one hard-to-fill role, Lever gives you adaptable, Al-powered hiring software that flexes as your team grows, your roles change, and your priorities shift. See it in Action Automate Operations Lever’s Advanced Automation makes it easy to set up common workflows to run on their own. Talent teams can set up interviews and collect candidate feedback with just a few clicks, and ready-to-go integrations help them recruit and hire faster. Learn More Make Onboarding a Breeze Between compliance, paperwork, and manual tasks, onboarding can feel like a lot. Change that with Lever. Built in I-9 and E-Verify, customizable workflows, and intelligent automation eliminate repetitive tasks so your team can focus on what matters and your new hires feel confident from day one. Learn More Empower Talent Teams Optimize recruiting and hiring processes with Lever’s Advanced HR. A ready-to-use Workday integration helps cut down on repetitive tasks so your talent teams can spend more time on important work – finding and hiring great people. Learn More Great Teams Start with Great Interviews The interview process = the most important part to making efficient, equitable, and effective hiring decisions. See how teams using AI Interview Companion are transforming the way they assess and hire candidates. Learn More Communicate with Candidates in Real Time Candidate Texting enables you and your talent team to directly connect with contacts in your pipeline, deliver stellar candidate experiences, streamline your nurturing efforts, and shave hours off your work week. Learn More Boost Your Application Completion Rate Career Site Builder empowers hiring teams to build on-brand, visually compelling careers pages in a matter of minutes. Using our WYSIWYG editor, you can showcase your employer branding, share your company story and mission, and entice active job seekers to apply. Learn More Award-Winning Recruiting Software Lever is rated a top HR software, leader in mid-market, and a highest satisfaction product.
Learn more about our ATS + CRM solution. Ready to Kick Start Your Hiring? Get a Quote Solutions Applicant Tracking System AI Interview Companion AI Screening Companion Onboarding Recruitment Analytics Recruitment Automation Recruitment Marketing High-Volume Hiring All Solutions Explore Pricing Request a Demo Content Library Events Webinars Blog Partner Integrations Marketplace Compare & Choose Lever vs. Ashby Lever vs. Greenhouse Lever vs. Workable Lever vs. SmartRecruiters iCIMS vs. SmartRecruiters Greenhouse vs Ashby Greenhouse Alternatives Ashby Alternatives Company About Us Customers Careers Contact Us Support Help Center Product Status Support Connect with Us Privacy Policy Terms of Use Security © 2025 Employ Inc. All rights reserved. Employ, JazzHR, Lever, and Jobvite are registered trademarks of Employ, Inc. Terms and conditions, features, support, pricing, and service options subject to change without notice. | 2026-01-13T09:29:41 |
https://ftp.gnu.org/old-gnu/gnotary/client/ | Index of /old-gnu/gnotary/client Index of /old-gnu/gnotary/client Name Last modified Size Description Parent Directory - 0.1/ 2005-08-27 05:55 - Apache/2.4.52 (Trisquel_GNU/Linux) Server at ftp.gnu.org Port 443 | 2026-01-13T09:29:41 |
https://news.google.com/?tab=in | html,body{height:100%;overflow:hidden}body{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale;color:rgba(0,0,0,0.87);font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif;margin:0;-webkit-text-size-adjust:100%;-moz-text-size-adjust:100%;-ms-text-size-adjust:100%;text-size-adjust:100%}textarea{font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif}a{text-decoration:none;color:#2962ff}img{border:none}*{-webkit-tap-highlight-color:transparent}#apps-debug-tracers{display:none}.MCcOAc{bottom:0;left:0;position:absolute;right:0;top:0;overflow:hidden;z-index:1}.MCcOAc>.pGxpHc{-webkit-flex-shrink:0;flex-shrink:0;-webkit-box-flex:0;-webkit-flex-grow:0;flex-grow:0}.IqBfM>.HLlAHb{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-box;display:-webkit-flex;display:flex;height:60px;position:absolute;right:16px;top:0;z-index:9999}.VUoKZ{display:none;position:absolute;top:0;left:0;right:0;height:3px;z-index:1001}.TRHLAc{position:absolute;top:0;left:0;width:25%;height:100%;background:#68e;-webkit-transform:scaleX(0);-ms-transform:scaleX(0);transform:scaleX(0)}.TRHLAc{-webkit-transform-origin:0 0;-ms-transform-origin:0 0;transform-origin:0 0}.mIM26c .VUoKZ{display:block}.mIM26c .TRHLAc{-webkit-animation:boqChromeapiPageProgressAnimation 1s infinite;animation:boqChromeapiPageProgressAnimation 1s infinite;-webkit-animation-timing-function:cubic-bezier(.4,0,1,1);animation-timing-function:cubic-bezier(.4,0,1,1);-webkit-animation-delay:.1s;animation-delay:.1s}.ghyPEc .VUoKZ{position:fixed}@-webkit-keyframes boqChromeapiPageProgressAnimation{0%{-webkit-transform:scaleX(0);transform:scaleX(0)}50%{-webkit-transform:scaleX(5);transform:scaleX(5)}100%{-webkit-transform:scaleX(5) translateX(100%);transform:scaleX(5) translateX(100%)}}@keyframes boqChromeapiPageProgressAnimation{0%{-webkit-transform:scaleX(0);transform:scaleX(0)}50%{-webkit-transform:scaleX(5);transform:scaleX(5)}100%{-webkit-transform:scaleX(5) translateX(100%);transform:scaleX(5) translateX(100%)}}.zQTmif{height:100%}.MCcOAc{display:-webkit-box;display:-webkit-flex;display:flex;-webkit-box-orient:vertical;-webkit-box-direction:normal;-webkit-flex-direction:column;flex-direction:column}.IqBfM{bottom:auto;height:100%;right:auto;width:auto}.kFwPee{height:100%}.ydMMEb{width:100%}.SSPGKf{display:block;overflow-y:hidden;z-index:1}.eejsDc{overflow-y:auto;-webkit-overflow-scrolling:touch}:root{--boq-chrometransition-background:#eee;--boq-chrometransition-active-background-opacity:0.8}.KL4X6e{background:var(--boq-chrometransition-background);bottom:0;left:0;opacity:0;position:absolute;right:0;top:0}.TuA45b{opacity:var(--boq-chrometransition-active-background-opacity)}body{--gn-c-background:var(--gm3-sys-color-background,#fff);--gn-c-error:var(--gm3-sys-color-error,#b3261e);--gn-c-error-container:var(--gm3-sys-color-error-container,#f9dedc);--gn-c-inverse-on-surface:var(--gm3-sys-color-inverse-on-surface,#f2f2f2);--gn-c-inverse-primary:var(--gm3-sys-color-inverse-primary,#a8c7fa);--gn-c-inverse-surface:var(--gm3-sys-color-inverse-surface,#303030);--gn-c-on-background:var(--gm3-sys-color-on-background,#1f1f1f);--gn-c-on-error:var(--gm3-sys-color-on-error,#fff);--gn-c-on-error-container:var(--gm3-sys-color-on-error-container,#8c1d18);--gn-c-on-primary:var(--gm3-sys-color-on-primary,#fff);--gn-c-on-primary-container:var(--gm3-sys-color-on-primary-container,#0842a0);--gn-c-on-primary-fixed:var(--gm3-sys-color-on-primary-fixed,#041e49);--gn-c-on-primary-fixed-variant:var(--gm3-sys-color-on-primary-fixed-variant,#0842a0);--gn-c-on-secondary:var(--gm3-sys-color-on-secondary,#fff);--gn-c-on-secondary-container:var(--gm3-sys-color-on-secondary-container,#004a77);--gn-c-on-secondary-fixed:var(--gm3-sys-color-on-secondary-fixed,#001d35);--gn-c-on-secondary-fixed-variant:var(--gm3-sys-color-on-secondary-fixed-variant,#004a77);--gn-c-on-surface:var(--gm3-sys-color-on-surface,#1f1f1f);--gn-c-on-surface-variant:var(--gm3-sys-color-on-surface-variant,#444746);--gn-c-on-tertiary:var(--gm3-sys-color-on-tertiary,#fff);--gn-c-on-tertiary-container:var(--gm3-sys-color-on-tertiary-container,#0f5223);--gn-c-on-tertiary-fixed:var(--gm3-sys-color-on-tertiary-fixed,#072711);--gn-c-on-tertiary-fixed-variant:var(--gm3-sys-color-on-tertiary-fixed-variant,#0f5223);--gn-c-outline:var(--gm3-sys-color-outline,#747775);--gn-c-outline-variant:var(--gm3-sys-color-outline-variant,#c4c7c5);--gn-c-primary:var(--gm3-sys-color-primary,#0b57d0);--gn-c-primary-container:var(--gm3-sys-color-primary-container,#d3e3fd);--gn-c-primary-fixed:var(--gm3-sys-color-primary-fixed,#d3e3fd);--gn-c-primary-fixed-dim:var(--gm3-sys-color-primary-fixed-dim,#a8c7fa);--gn-c-scrim:var(--gm3-sys-color-scrim,#000);--gn-c-secondary:var(--gm3-sys-color-secondary,#00639b);--gn-c-secondary-container:var(--gm3-sys-color-secondary-container,#c2e7ff);--gn-c-secondary-fixed:var(--gm3-sys-color-secondary-fixed,#c2e7ff);--gn-c-secondary-fixed-dim:var(--gm3-sys-color-secondary-fixed-dim,#7fcfff);--gn-c-shadow:var(--gm3-sys-color-shadow,#000);--gn-c-surface:var(--gm3-sys-color-surface,#fff);--gn-c-surface-bright:var(--gm3-sys-color-surface-bright,#fff);--gn-c-surface-container:var(--gm3-sys-color-surface-container,#f0f4f9);--gn-c-surface-container-high:var(--gm3-sys-color-surface-container-high,#e9eef6);--gn-c-surface-container-highest:var(--gm3-sys-color-surface-container-highest,#dde3ea);--gn-c-surface-container-low:var(--gm3-sys-color-surface-container-low,#f8fafd);--gn-c-surface-container-lowest:var(--gm3-sys-color-surface-container-lowest,#fff);--gn-c-surface-dim:var(--gm3-sys-color-surface-dim,#d3dbe5);--gn-c-surface-tint:var(--gm3-sys-color-surface-tint,#6991d6);--gn-c-surface-variant:var(--gm3-sys-color-surface-variant,#e1e3e1);--gn-c-tertiary:var(--gm3-sys-color-tertiary,#146c2e);--gn-c-tertiary-container:var(--gm3-sys-color-tertiary-container,#c4eed0);--gn-c-tertiary-fixed:var(--gm3-sys-color-tertiary-fixed,#c4eed0);--gn-c-tertiary-fixed-dim:var(--gm3-sys-color-tertiary-fixed-dim,#6dd58c);--gn-c-ai-analog:#a7edff;--gn-c-ai-complement:#fdadee;--gn-c-ai-gradient-stop-1:#4285f4;--gn-c-ai-gradient-stop-2:#9b72cb;--gn-c-ai-gradient-stop-3:#d96570;--gn-c-ai-gradient-stop-final:#ffffff;--gn-c-ogb-background:#ffffff;--gn-c-toast-background:rgb(32,33,36);--gn-c-toast-color:rgb(232,234,237);--gn-c-color-link:rgb(26,115,232);--gn-c-banner-background:rgb(210,227,252);--gn-c-banner-text:#1f1f1f;--gn-c-adv-search-text:rgb(60,64,67);--gn-c-adv-search-outline:rgb(218,220,224);--gn-c-adv-search-underline:#e0e0e0;--gn-c-adv-search-error-underline:rgb(197,34,31);--gn-c-divider:#e3e3e3;--gn-c-jump-button-unselected-bg:var(--gm3-sys-color-primary-container,#d3e3fd);--gn-c-jump-button-unselected-text:var(--gm3-sys-color-on-primary-container,#0842a0);--gn-c-jump-button-unselected-bg-scrolled:var(--gm3-sys-color-surface,#fff);--gn-c-jump-button-selected-bg-scrolled:var(--gm3-sys-color-primary-fixed-dim,#a8c7fa);--gn-c-jump-button-selected-text-scrolled:var(--gm3-sys-color-on-primary-fixed,#041e49);--gn-c-jump-button-container-bg:#e5e9f8;--gn-c-jump-button-arrow-icon-bg:var(--gm3-sys-color-inverse-on-surface,#f2f2f2)}body.dm7YTc{--gn-c-background:var(--gm3-sys-color-background,#131314);--gn-c-error:var(--gm3-sys-color-error,#f2b8b5);--gn-c-error-container:var(--gm3-sys-color-error-container,#8c1d18);--gn-c-inverse-on-surface:var(--gm3-sys-color-inverse-on-surface,#303030);--gn-c-inverse-primary:var(--gm3-sys-color-inverse-primary,#0b57d0);--gn-c-inverse-surface:var(--gm3-sys-color-inverse-surface,#e3e3e3);--gn-c-on-background:var(--gm3-sys-color-on-background,#e3e3e3);--gn-c-on-error:var(--gm3-sys-color-on-error,#601410);--gn-c-on-error-container:var(--gm3-sys-color-on-error-container,#f9dedc);--gn-c-on-primary:var(--gm3-sys-color-on-primary,#062e6f);--gn-c-on-primary-container:var(--gm3-sys-color-on-primary-container,#d3e3fd);--gn-c-on-primary-fixed:var(--gm3-sys-color-on-primary-fixed,#041e49);--gn-c-on-primary-fixed-variant:var(--gm3-sys-color-on-primary-fixed-variant,#0842a0);--gn-c-on-secondary:var(--gm3-sys-color-on-secondary,#035);--gn-c-on-secondary-container:var(--gm3-sys-color-on-secondary-container,#c2e7ff);--gn-c-on-secondary-fixed:var(--gm3-sys-color-on-secondary-fixed,#001d35);--gn-c-on-secondary-fixed-variant:var(--gm3-sys-color-on-secondary-fixed-variant,#004a77);--gn-c-on-surface:var(--gm3-sys-color-on-surface,#e3e3e3);--gn-c-on-surface-variant:var(--gm3-sys-color-on-surface-variant,#c4c7c5);--gn-c-on-tertiary:var(--gm3-sys-color-on-tertiary,#0a3818);--gn-c-on-tertiary-container:var(--gm3-sys-color-on-tertiary-container,#c4eed0);--gn-c-on-tertiary-fixed:var(--gm3-sys-color-on-tertiary-fixed,#072711);--gn-c-on-tertiary-fixed-variant:var(--gm3-sys-color-on-tertiary-fixed-variant,#0f5223);--gn-c-outline:var(--gm3-sys-color-outline,#8e918f);--gn-c-outline-variant:var(--gm3-sys-color-outline-variant,#444746);--gn-c-primary:var(--gm3-sys-color-primary,#a8c7fa);--gn-c-primary-container:var(--gm3-sys-color-primary-container,#0842a0);--gn-c-primary-fixed:var(--gm3-sys-color-primary-fixed,#d3e3fd);--gn-c-primary-fixed-dim:var(--gm3-sys-color-primary-fixed-dim,#a8c7fa);--gn-c-scrim:var(--gm3-sys-color-scrim,#000);--gn-c-secondary:var(--gm3-sys-color-secondary,#7fcfff);--gn-c-secondary-container:var(--gm3-sys-color-secondary-container,#004a77);--gn-c-secondary-fixed:var(--gm3-sys-color-secondary-fixed,#c2e7ff);--gn-c-secondary-fixed-dim:var(--gm3-sys-color-secondary-fixed-dim,#7fcfff);--gn-c-shadow:var(--gm3-sys-color-shadow,#000);--gn-c-surface:var(--gm3-sys-color-surface,#131314);--gn-c-surface-bright:var(--gm3-sys-color-surface-bright,#37393b);--gn-c-surface-container:var(--gm3-sys-color-surface-container,#1e1f20);--gn-c-surface-container-high:var(--gm3-sys-color-surface-container-high,#282a2c);--gn-c-surface-container-highest:var(--gm3-sys-color-surface-container-highest,#333537);--gn-c-surface-container-low:var(--gm3-sys-color-surface-container-low,#1b1b1b);--gn-c-surface-container-lowest:var(--gm3-sys-color-surface-container-lowest,#0e0e0e);--gn-c-surface-dim:var(--gm3-sys-color-surface-dim,#131314);--gn-c-surface-tint:var(--gm3-sys-color-surface-tint,#d1e1ff);--gn-c-surface-variant:var(--gm3-sys-color-surface-variant,#444746);--gn-c-tertiary:var(--gm3-sys-color-tertiary,#6dd58c);--gn-c-tertiary-container:var(--gm3-sys-color-tertiary-container,#0f5223);--gn-c-tertiary-fixed:var(--gm3-sys-color-tertiary-fixed,#c4eed0);--gn-c-tertiary-fixed-dim:var(--gm3-sys-color-tertiary-fixed-dim,#6dd58c);--gn-c-ai-analog:#004e5b;--gn-c-ai-complement:#53164f;--gn-c-ai-gradient-stop-1:#649eff;--gn-c-ai-gradient-stop-2:#b885f3;--gn-c-ai-gradient-stop-3:#fd8a95;--gn-c-ai-gradient-stop-final:#1b1c1d;--gn-c-ogb-background:rgb(32,33,36);--gn-c-toast-background:#ffffff;--gn-c-toast-color:rgb(60,64,67);--gn-c-color-link:rgb(138,180,248);--gn-c-banner-background:#2a4165;--gn-c-banner-text:#e3e3e3;--gn-c-adv-search-text:rgb(232,234,237);--gn-c-adv-search-outline:rgb(95,99,104);--gn-c-adv-search-underline:#5f6368;--gn-c-adv-search-error-underline:rgb(246,174,169);--gn-c-divider:#5e5e5e;--gn-c-jump-button-unselected-bg:var(--gm3-sys-color-surface-container-highest,#333537);--gn-c-jump-button-unselected-text:var(--gm3-sys-color-on-surface,#e3e3e3);--gn-c-jump-button-unselected-bg-scrolled:var(--gm3-sys-color-surface-container-highest,#333537);--gn-c-jump-button-selected-bg-scrolled:var(--gm3-sys-color-primary,#a8c7fa);--gn-c-jump-button-selected-text-scrolled:var(--gm3-sys-color-on-primary,#062e6f);--gn-c-jump-button-container-bg:var(--gm3-sys-color-surface-container-high,#282a2c);--gn-c-jump-button-arrow-icon-bg:var(--gm3-sys-color-surface-variant,#444746)}body.dm7YTc .Y5O54e{display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;position:relative}body.dm7YTc .Y5O54e[hidden]{display:none}body.dm7YTc .Y5O54e .UMrnmb-lP5Lpb-yrriRe{width:inherit}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b{padding-left:16px;padding-right:16px}[dir=rtl] body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b[dir=rtl]{padding-left:16px;padding-right:16px}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb.VfPpkd-StrnGf-rymPhb-OWXEXe-Bz112c-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-f7MjDc{margin-left:0;margin-right:8px}[dir=rtl] body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb.VfPpkd-StrnGf-rymPhb-OWXEXe-Bz112c-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-f7MjDc,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb.VfPpkd-StrnGf-rymPhb-OWXEXe-Bz112c-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-f7MjDc[dir=rtl]{margin-left:8px;margin-right:0}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb.UMrnmb-h0T7hb-M1Soyc-Bz112c .VfPpkd-StrnGf-rymPhb-ibnC6b{padding-left:48px;padding-right:16px}[dir=rtl] body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb.UMrnmb-h0T7hb-M1Soyc-Bz112c .VfPpkd-StrnGf-rymPhb-ibnC6b,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb.UMrnmb-h0T7hb-M1Soyc-Bz112c .VfPpkd-StrnGf-rymPhb-ibnC6b[dir=rtl]{padding-left:16px;padding-right:48px}body.dm7YTc .Y5O54e .VfPpkd-xl07Ob-XxIAqe-OWXEXe-uxVfW-FNFY6c-uFfGwd{border-top-left-radius:0;border-top-right-radius:0}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:hover .VfPpkd-fmcmS-OyKIhb::before,body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-fmcmS-OyKIhb::before{opacity:.08;opacity:var(--mdc-ripple-hover-opacity,.08)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-fmcmS-OyKIhb::before,body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-fmcmS-OyKIhb::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe .VfPpkd-fmcmS-OyKIhb::before,body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe .VfPpkd-fmcmS-OyKIhb::after{background-color:rgb(241,243,244);background-color:var(--mdc-ripple-color,rgb(241,243,244))}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd,body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe .VfPpkd-fmcmS-wGMbrd{caret-color:rgb(138,180,248)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd{color:rgb(232,234,237)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me){background-color:rgb(60,64,67)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(189,193,198)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(248,249,250)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgb(248,249,250)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-RWgCYc-ksKsZd::after{border-bottom-color:rgb(138,180,248)}@media all{body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{color:rgb(189,193,198)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-moz-placeholder{color:rgb(189,193,198)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgb(189,193,198)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{color:rgb(189,193,198)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::placeholder{color:rgb(189,193,198)}}@media all{body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgb(189,193,198)}}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-M1Soyc{color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me{background-color:rgba(232,234,237,.04)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-NLUYnc-V67aGc{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-TvZj5c-OWXEXe-M1Soyc{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd,body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{color:rgba(232,234,237,.38)}@media all{body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd::-moz-placeholder{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd::placeholder{color:rgba(232,234,237,.38)}}@media all{body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgba(232,234,237,.38)}}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{color:rgba(232,234,237,.38)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(138,180,248)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc .VfPpkd-fmcmS-wGMbrd{caret-color:rgb(246,174,169)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgb(242,139,130)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgb(242,139,130)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgb(246,174,169)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-RWgCYc-ksKsZd::after{border-bottom-color:rgb(246,174,169)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(246,174,169)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgb(246,174,169)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgb(246,174,169)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgb(246,174,169)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-NLUYnc-V67aGc{color:rgb(138,180,248)}body.dm7YTc .Y5O54e .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(246,174,169)}body.dm7YTc .Y5O54e .VfPpkd-xl07Ob-XxIAqe{-webkit-box-shadow:0 2px 1px -1px rgba(0,0,0,.2),0 1px 1px 0 rgba(0,0,0,.14),0 1px 3px 0 rgba(0,0,0,.12);box-shadow:0 2px 1px -1px rgba(0,0,0,.2),0 1px 1px 0 rgba(0,0,0,.14),0 1px 3px 0 rgba(0,0,0,.12);background-color:rgb(32,33,36)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb{font-family:Roboto,Arial,sans-serif;line-height:1.5rem;font-size:1rem;letter-spacing:.00625em;font-weight:400;color:rgb(232,234,237);position:relative}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-IhFlZd{color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-b9t22c,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-fpDzbe-fmcmS,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-L8ivfd-fmcmS{color:rgb(232,234,237)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-b9t22c{opacity:.38}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-pXU01b{color:rgb(232,234,237)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd .VfPpkd-StrnGf-rymPhb-f7MjDc,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-pXU01b .VfPpkd-StrnGf-rymPhb-f7MjDc{color:rgb(232,234,237)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd .VfPpkd-StrnGf-rymPhb-pZXsl::before{opacity:0}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd{background-color:rgba(138,180,248,.24)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd .VfPpkd-StrnGf-rymPhb-pZXsl::after{background-color:rgb(138,180,248);background-color:var(--mdc-ripple-color,rgb(138,180,248))}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd:hover .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-StrnGf-rymPhb-pZXsl::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-StrnGf-rymPhb-pZXsl::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-StrnGf-rymPhb-pZXsl::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-StrnGf-rymPhb-pZXsl::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.1;opacity:var(--mdc-ripple-press-opacity,.1)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.1)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-L8ivfd-fmcmS{color:rgb(154,160,166)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-clz4Ic{border-bottom-color:rgba(232,234,237,.12)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-f7MjDc{color:rgb(232,234,237)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-pZXsl::after{background-color:rgb(232,234,237);background-color:var(--mdc-ripple-color,rgb(232,234,237))}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b:hover .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-StrnGf-rymPhb-pZXsl::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-StrnGf-rymPhb-pZXsl::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-StrnGf-rymPhb-pZXsl::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-StrnGf-rymPhb-pZXsl::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.1;opacity:var(--mdc-ripple-press-opacity,.1)}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.1)}@media (-ms-high-contrast:active),screen and (forced-colors:active){body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-b9t22c,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-fpDzbe-fmcmS,body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-L8ivfd-fmcmS{color:GrayText}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-b9t22c{opacity:1}}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-BFbNVe-bF1uUb{width:100%;height:100%;top:0;left:0}body.dm7YTc .Y5O54e .VfPpkd-StrnGf-rymPhb .VfPpkd-BFbNVe-bF1uUb{opacity:.08}body.dm7YTc .NGdKgb{display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;position:relative}body.dm7YTc .NGdKgb[hidden]{display:none}body.dm7YTc .NGdKgb .UMrnmb-lP5Lpb-yrriRe{width:inherit}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b{padding-left:16px;padding-right:16px}[dir=rtl] body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b[dir=rtl]{padding-left:16px;padding-right:16px}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb.VfPpkd-StrnGf-rymPhb-OWXEXe-Bz112c-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-f7MjDc{margin-left:0;margin-right:8px}[dir=rtl] body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb.VfPpkd-StrnGf-rymPhb-OWXEXe-Bz112c-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-f7MjDc,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb.VfPpkd-StrnGf-rymPhb-OWXEXe-Bz112c-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-f7MjDc[dir=rtl]{margin-left:8px;margin-right:0}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb.UMrnmb-h0T7hb-M1Soyc-Bz112c .VfPpkd-StrnGf-rymPhb-ibnC6b{padding-left:48px;padding-right:16px}[dir=rtl] body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb.UMrnmb-h0T7hb-M1Soyc-Bz112c .VfPpkd-StrnGf-rymPhb-ibnC6b,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb.UMrnmb-h0T7hb-M1Soyc-Bz112c .VfPpkd-StrnGf-rymPhb-ibnC6b[dir=rtl]{padding-left:16px;padding-right:48px}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd{color:rgb(232,234,237);color:var(--gm-outlinedtextfield-ink-color,rgb(232,234,237))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe .VfPpkd-fmcmS-wGMbrd{caret-color:rgb(138,180,248);caret-color:var(--gm-outlinedtextfield-caret-color,rgb(138,180,248))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgb(154,160,166);color:var(--gm-outlinedtextfield-helper-text-color,rgb(154,160,166))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{color:rgb(154,160,166)}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(154,160,166);color:var(--gm-outlinedtextfield-label-color,rgb(154,160,166))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(248,249,250)}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Brv4Fb,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Ra9xwd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-MpmGFe{border-color:rgb(189,193,198);border-color:var(--gm-outlinedtextfield-outline-color,rgb(189,193,198))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Ra9xwd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe{border-color:rgb(248,249,250)}@media all{body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{color:rgb(189,193,198);color:var(--gm-outlinedtextfield-placeholder-color,rgb(189,193,198))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-moz-placeholder{color:rgb(189,193,198);color:var(--gm-outlinedtextfield-placeholder-color,rgb(189,193,198))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgb(189,193,198);color:var(--gm-outlinedtextfield-placeholder-color,rgb(189,193,198))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{color:rgb(189,193,198);color:var(--gm-outlinedtextfield-placeholder-color,rgb(189,193,198))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::placeholder{color:rgb(189,193,198);color:var(--gm-outlinedtextfield-placeholder-color,rgb(189,193,198))}}@media all{body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgb(189,193,198);color:var(--gm-outlinedtextfield-placeholder-color,rgb(189,193,198))}}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{color:rgb(154,160,166);color:var(--gm-outlinedtextfield-prefix-color,rgb(154,160,166))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{color:rgb(154,160,166);color:var(--gm-outlinedtextfield-suffix-color,rgb(154,160,166))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-M1Soyc{color:rgb(154,160,166)}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgb(154,160,166)}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-ink-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-NSFCdd-Brv4Fb,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-NSFCdd-Ra9xwd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-NSFCdd-MpmGFe{border-color:rgba(232,234,237,.12);border-color:var(--gm-outlinedtextfield-outline-color--disabled,rgba(232,234,237,.12))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-NLUYnc-V67aGc{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-label-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-TvZj5c-OWXEXe-M1Soyc{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-icon-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-icon-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-helper-text-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-character-counter-color--disabled,rgba(232,234,237,.38))}@media all{body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-placeholder-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd::-moz-placeholder{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-placeholder-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-placeholder-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-placeholder-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd::placeholder{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-placeholder-color--disabled,rgba(232,234,237,.38))}}@media all{body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-placeholder-color--disabled,rgba(232,234,237,.38))}}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-prefix-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{color:rgba(232,234,237,.38);color:var(--gm-outlinedtextfield-suffix-color--disabled,rgba(232,234,237,.38))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Brv4Fb,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Ra9xwd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-MpmGFe{border-color:rgb(138,180,248);border-color:var(--gm-outlinedtextfield-outline-color--stateful,rgb(138,180,248))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(138,180,248);color:var(--gm-outlinedtextfield-label-color--stateful,rgb(138,180,248))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc .VfPpkd-fmcmS-wGMbrd{caret-color:rgb(242,139,130);caret-color:var(--gm-outlinedtextfield-caret-color--error,rgb(242,139,130))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgb(242,139,130);color:var(--gm-outlinedtextfield-helper-text-color--error,rgb(242,139,130))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgb(246,174,169)}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(246,174,169)}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:hover:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgb(246,174,169)}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Ra9xwd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe{border-color:rgb(246,174,169)}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Brv4Fb,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Ra9xwd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-MpmGFe{border-color:rgb(242,139,130);border-color:var(--gm-outlinedtextfield-outline-color--error,rgb(242,139,130))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgb(242,139,130);color:var(--gm-outlinedtextfield-icon-color--error,rgb(242,139,130))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Brv4Fb,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Ra9xwd,body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-MpmGFe{border-color:rgb(242,139,130);border-color:var(--gm-outlinedtextfield-outline-color--error-stateful,rgb(242,139,130))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-NLUYnc-V67aGc{color:rgb(138,180,248);color:var(--gm-outlinedtextfield-label-color--stateful,rgb(138,180,248))}body.dm7YTc .NGdKgb .VfPpkd-fmcmS-yrriRe.VfPpkd-fmcmS-yrriRe-OWXEXe-UJflGc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgb(242,139,130);color:var(--gm-outlinedtextfield-label-color--error,rgb(242,139,130))}body.dm7YTc .NGdKgb .VfPpkd-xl07Ob-XxIAqe{-webkit-box-shadow:0 2px 1px -1px rgba(0,0,0,.2),0 1px 1px 0 rgba(0,0,0,.14),0 1px 3px 0 rgba(0,0,0,.12);box-shadow:0 2px 1px -1px rgba(0,0,0,.2),0 1px 1px 0 rgba(0,0,0,.14),0 1px 3px 0 rgba(0,0,0,.12);background-color:rgb(32,33,36);margin-bottom:8px}body.dm7YTc .NGdKgb.UMrnmb-h0T7hb-OWXEXe-di8rgd-V67aGc .VfPpkd-xl07Ob-XxIAqe,body.dm7YTc .NGdKgb .VfPpkd-xl07Ob-XxIAqe-OWXEXe-uxVfW-FNFY6c-uFfGwd{margin-bottom:0}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb{font-family:Roboto,Arial,sans-serif;line-height:1.5rem;font-size:1rem;letter-spacing:.00625em;font-weight:400;color:rgb(232,234,237);position:relative}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-IhFlZd{color:rgb(154,160,166)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-b9t22c,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-fpDzbe-fmcmS,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-L8ivfd-fmcmS{color:rgb(232,234,237)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-b9t22c{opacity:.38}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-pXU01b{color:rgb(232,234,237)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd .VfPpkd-StrnGf-rymPhb-f7MjDc,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-pXU01b .VfPpkd-StrnGf-rymPhb-f7MjDc{color:rgb(232,234,237)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd .VfPpkd-StrnGf-rymPhb-pZXsl::before{opacity:0}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd{background-color:rgba(138,180,248,.24)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd .VfPpkd-StrnGf-rymPhb-pZXsl::after{background-color:rgb(138,180,248);background-color:var(--mdc-ripple-color,rgb(138,180,248))}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd:hover .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-StrnGf-rymPhb-pZXsl::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-StrnGf-rymPhb-pZXsl::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-StrnGf-rymPhb-pZXsl::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-StrnGf-rymPhb-pZXsl::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.1;opacity:var(--mdc-ripple-press-opacity,.1)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-gk6SMd.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.1)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-L8ivfd-fmcmS{color:rgb(154,160,166)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-clz4Ic{border-bottom-color:rgba(232,234,237,.12)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-f7MjDc{color:rgb(232,234,237)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b .VfPpkd-StrnGf-rymPhb-pZXsl::after{background-color:rgb(232,234,237);background-color:var(--mdc-ripple-color,rgb(232,234,237))}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b:hover .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-StrnGf-rymPhb-pZXsl::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-StrnGf-rymPhb-pZXsl::before,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-StrnGf-rymPhb-pZXsl::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-StrnGf-rymPhb-pZXsl::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-StrnGf-rymPhb-pZXsl::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.1;opacity:var(--mdc-ripple-press-opacity,.1)}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.1)}@media (-ms-high-contrast:active),screen and (forced-colors:active){body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-b9t22c,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-fpDzbe-fmcmS,body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-L8ivfd-fmcmS{color:GrayText}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-StrnGf-rymPhb-ibnC6b-OWXEXe-OWB6Me .VfPpkd-StrnGf-rymPhb-b9t22c{opacity:1}}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-BFbNVe-bF1uUb{width:100%;height:100%;top:0;left:0}body.dm7YTc .NGdKgb .VfPpkd-StrnGf-rymPhb .VfPpkd-BFbNVe-bF1uUb{opacity:.08}body.dm7YTc .DUonjc{background-color:rgb(32,33,36);border-bottom-color:rgb(95,99,104)}body.dm7YTc .DUonjc .VfPpkd-WLXbod{background-color:rgb(32,33,36)}body.dm7YTc .DUonjc .VfPpkd-Rj7Y9b{color:rgb(232,234,237)}body.dm7YTc .DUonjc .VfPpkd-WLXbod{border-bottom-color:rgb(95,99,104)}body.dm7YTc .DUonjc .VfPpkd-r7nwK{color:rgb(32,33,36)}body.dm7YTc .DUonjc .VfPpkd-r7nwK{background-color:rgb(138,180,248)}body.dm7YTc .DUonjc .VfPpkd-LgbsSe:not(:disabled){background-color:transparent}body.dm7YTc .DUonjc .VfPpkd-LgbsSe:not(:disabled){color:rgb(138,180,248);color:var(--gm-colortextbutton-ink-color,rgb(138,180,248))}body.dm7YTc .DUonjc .VfPpkd-LgbsSe:disabled{color:rgba(232,234,237,.38);color:var(--gm-colortextbutton-disabled-ink-color,rgba(232,234,237,.38))}body.dm7YTc .DUonjc .VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,body.dm7YTc .DUonjc .VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(138,180,248)}@media (-ms-high-contrast:active),screen and (forced-colors:active){body.dm7YTc .DUonjc .VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,body.dm7YTc .DUonjc .VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}body.dm7YTc .DUonjc .VfPpkd-LgbsSe:hover:not(:disabled),body.dm7YTc .DUonjc .VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),body.dm7YTc .DUonjc .VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),body.dm7YTc .DUonjc .VfPpkd-LgbsSe:active:not(:disabled){color:rgb(174,203,250);color:var(--gm-colortextbutton-ink-color--stateful,rgb(174,203,250))}body.dm7YTc .DUonjc .VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,body.dm7YTc .DUonjc .VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/software/jira/ai | Jira 中的 Rovo：人工智能功能 | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 免费获取 功能 所有功能 Jira 中的 Rovo Back 解决方案 Teams 用例 公司规模 Teams 营销 工程 设计 运营 IT 用例 入门 规划 活动管理 敏捷项目管理 计划管理 公司规模 Enterprise Back 产品指南 模板 模板 所有模板 软件开发 营销 设计 销售 运营 服务管理 人力资源 法律 IT 运营 金融 Jira Service Management 模板 Back 定价 更多 + 更少 - 免费获取 Back 免费获取 能实现近乎自主管理的项目 与其把精力花在搭建项目、分享更新、打破信息壁垒等工作上，倒不如让人工智能来处理这一切，这样您就能专注于更重要的事情？ 免费试用 Jira Jira：重塑项目管理 人工智能支持的工作流、企业级搜索功能以及现成可用的 Rovo 支持人员，均已无缝集成到 Jira 中。它是唯一一款能让团队更高效协作、以更少投入达成卓越成果的项目管理工具。 工作更加智能 释放您的全部潜力 现成可用的专业 Rovo 支持人员已准备就绪，助您的想法大放异彩。让它们助力您快速启动工作、管理细节，并为您的下一个战略举措提供建议。 探索支持人员 工作流构建器支持人员 只需使用日常语言，就能在 Jira 中为任何流程构建自定义工作流。 工作就绪检查器支持人员 通过确保工作内容清晰、完整，为团队进行规划和优先级排序，减少无效工作和后续会议。 面向开发人员的支持人员式人工智能 将 Jira 工作项转换为代码。Rovo Dev 可加速软件交付流程，并让开发者始终处于高效专注状态。 了解更多 加速工作效率 告别繁琐杂务，专注价值创造 重大成果的达成，从未像现在这样省时高效。Jira 的人工智能功能直接嵌入到您的工作流中，因此您可以在不打断工作节奏的情况下，完成工作的创建、跟踪与沟通。 工作创建 再也无需切换选项卡和复制粘贴了。Rovo 能从 Confluence、Slack、电子邮件、您的 IDE —甚至图片中 捕获工作信息。 Watch now → 工作分解 只需一键点击，Rovo 就能将工作分解为易于管理的任务，还会附带摘要和描述。 Watch now → 相关资源 自动呈现类似的 Jira 工作项和相关的 Confluence 页面，让利益相关者拥有启动工作所需的一切。 协同工作 通向更优质团队合作的捷径 让共享知识得以规模化传播，并加快整个组织的协同一致。获取准确信息和即时背景信息，以便做出更优决策并更快实现创新。 了解更多 Rovo 聊天 深入探索、快速上手、即刻行动—只需一句指令！ 浏览器扩展 在浏览器中使用 Rovo 聊天与搜索功能，让您随时随地都能持续学习。 定义 借助行内术语解释，轻松化解团队术语理解障碍，确保工作流畅推进。 See Rovo in Action Create work from anywhere Build automations fast Find work instantly Break down complex project Enrich work items with context Create work from anywhere Build automations fast Find work instantly Break down complex project Enrich work items with context 安全工作 尊重数据、守护隐私的人工智能 Rovo 秉持“隐私设计优先”原则，同时提供贴合实际的人工智能洞察信息—无论是在减少人工操作，还是在推进复杂项目规模化方面，都能发挥作用。 了解更多 安全 我们人工智能支持的功能会确保您的数据安全且私密。 透明 掌控您的数据并了解每项功能的工作方式。 可扩展 在整个组织中轻松加快关键业务工作流程。 能融入团队工作场景的人工智能 通过从您已连接的工具中提取更多背景信息，Jira 成为驱动更丰富人工智能洞察信息、实现更优成果的终极事实来源。 了解更多 常见问题解答 常见问题 谁能获取 Rovo？ 拥有 Jira、Confluence、Jira Service Management 或 Teamwork Collection 的 Standard、Premium 或 Enterprise Cloud 计划的客户可以获取 Rovo。 Atlassian Cloud 计划和团队合作集合中何时提供 Rovo？ Rovo 将于 2025 年 4 月开始在 Premium 和 Enterprise 计划中激活，Standard 计划将于今年晚些时候启用。如果您是 Atlassian 组织管理员，并希望在您的计划中提供 Rovo 后立即获取 Rovo，请填写上面的“联系我们”表单。 提交“联系我们”表单后，一旦您的云计划或 Teamwork Collection 中提供 Rovo，您将立即收到通知。如果您不需要抢先体验，则无需采取进一步的操作。 Rovo 需要人工智能吗？ Premium 和 Enterprise 计划中的所有产品（包括 Rovo）都会自动激活人工智能。如果您的组织尚未准备好使用人工智能，组织管理员可以将其 停用 。 如果您停用人工智能，Rovo 的核心应用（如搜索和工作室）仍将正常运行，但 人工智能支持的功能 （包括 Rovo 聊天和 Rovo 支持人员）将不可用。 如何在云计划或团队合作集合中提供 Rovo 之前体验它？ 要立即体验 Rovo，您可以使用您的主要工作电子邮件地址注册申请 免费试用 Confluence、Jira 和 Jira Service Management，包括 Rovo。 如果我的组织目前正在使用 Data Center，我是否可以使用 Rovo？ 要充分利用 Rovo 的所有人工智能功能（包括搜索、聊天、支持人员和工作室），需订阅 Atlassian Cloud Premium 或 Enterprise 计划。 如果您的组织尚未准备好迁移到云，Rovo Data Center 的 Confluence Data Center 和 Jira Data Center 连接器（即将推出）可实现 Data Center 和云环境之间的无缝数据同步，使客户能够在保持现有基础架构的同时利用基于云的人工智能功能。 Atlassian 如何保护客户数据？ 我们始终将隐私原则与企业价值观贯彻于 Rovo 的开发运营，正如我们在所有业务中的坚守。我们致力于构建有意义的数据管控体系、选择权及通知机制，以促进更开放的协作与更深入的团队合作。 这意味着我们的设计始终秉持隐私保护原则。您可以在我们的信任中心找到 现有的隐私原则 ，也可以在这里找到我们的 隐私政策 。 在哪里可以了解 Atlassian 的负责任技术方法？ 在 Atlassian Intelligence 的构建、部署与应用过程中，我们严格遵循负责任技术原则，该原则侧重于透明度、信任、问责制、以人为本及团队合作。这些原则有助于我们负责任地考虑和使用人工智能等技术，并与我们的公司价值观保持一致。 如需详细了解我们对负责任技术的方法和承诺，请访问 责任技术原则 。 无论您想构思出什么创意，Jira 都能助您将其实现 免费试用 Jira 企业 诚聘英才 活动 博文 投资者关系 Atlassian Foundation 徽标 新闻资料袋 联系我们 产品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket 查看所有免费产品 资源 技术支持 购买和许可 Atlassian 社区 知识库 Marketplace 我的帐户 创建支持请求单 学习 合作伙伴 培训和认证 文档 开发人员资源 企业服务 查看全部资源 版权所有 © 2025 Atlassian 隐私政策 条款 Impressum 选择语言 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:41 |
https://git-scm.com/book/ms/v2/Git-Basics-Working-with-Remotes | Git - Working with Remotes About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Getting Started 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Summary 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.5 Git Basics - Working with Remotes Working with Remotes To be able to collaborate on any Git project, you need to know how to manage your remote repositories. Remote repositories are versions of your project that are hosted on the Internet or network somewhere. You can have several of them, each of which generally is either read-only or read/write for you. Collaborating with others involves managing these remote repositories and pushing and pulling data to and from them when you need to share work. Managing remote repositories includes knowing how to add remote repositories, remove remotes that are no longer valid, manage various remote branches and define them as being tracked or not, and more. In this section, we’ll cover some of these remote-management skills. Note Remote repositories can be on your local machine. It is entirely possible that you can be working with a “remote” repository that is, in fact, on the same host you are. The word “remote” does not necessarily imply that the repository is somewhere else on the network or Internet, only that it is elsewhere. Working with such a remote repository would still involve all the standard pushing, pulling and fetching operations as with any other remote. Showing Your Remotes To see which remote servers you have configured, you can run the git remote command. It lists the shortnames of each remote handle you’ve specified. If you’ve cloned your repository, you should at least see origin — that is the default name Git gives to the server you cloned from: $ git clone https://github.com/schacon/ticgit Cloning into 'ticgit'... remote: Reusing existing pack: 1857, done. remote: Total 1857 (delta 0), reused 0 (delta 0) Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done. Resolving deltas: 100% (772/772), done. Checking connectivity... done. $ cd ticgit $ git remote origin You can also specify -v , which shows you the URLs that Git has stored for the shortname to be used when reading and writing to that remote: $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) If you have more than one remote, the command lists them all. For example, a repository with multiple remotes for working with several collaborators might look something like this. $ cd grit $ git remote -v bakkdoor https://github.com/bakkdoor/grit (fetch) bakkdoor https://github.com/bakkdoor/grit (push) cho45 https://github.com/cho45/grit (fetch) cho45 https://github.com/cho45/grit (push) defunkt https://github.com/defunkt/grit (fetch) defunkt https://github.com/defunkt/grit (push) koke git://github.com/koke/grit.git (fetch) koke git://github.com/koke/grit.git (push) origin git@github.com:mojombo/grit.git (fetch) origin git@github.com:mojombo/grit.git (push) This means we can pull contributions from any of these users pretty easily. We may additionally have permission to push to one or more of these, though we can’t tell that here. Notice that these remotes use a variety of protocols; we’ll cover more about this in Getting Git on a Server . Adding Remote Repositories We’ve mentioned and given some demonstrations of how the git clone command implicitly adds the origin remote for you. Here’s how to add a new remote explicitly. To add a new remote Git repository as a shortname you can reference easily, run git remote add <shortname> <url> : $ git remote origin $ git remote add pb https://github.com/paulboone/ticgit $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) pb https://github.com/paulboone/ticgit (fetch) pb https://github.com/paulboone/ticgit (push) Now you can use the string pb on the command line in lieu of the whole URL. For example, if you want to fetch all the information that Paul has but that you don’t yet have in your repository, you can run git fetch pb : $ git fetch pb remote: Counting objects: 43, done. remote: Compressing objects: 100% (36/36), done. remote: Total 43 (delta 10), reused 31 (delta 5) Unpacking objects: 100% (43/43), done. From https://github.com/paulboone/ticgit * [new branch] master -> pb/master * [new branch] ticgit -> pb/ticgit Paul’s master branch is now accessible locally as pb/master — you can merge it into one of your branches, or you can check out a local branch at that point if you want to inspect it. We’ll go over what branches are and how to use them in much more detail in Git Branching . Fetching and Pulling from Your Remotes As you just saw, to get data from your remote projects, you can run: $ git fetch <remote> The command goes out to that remote project and pulls down all the data from that remote project that you don’t have yet. After you do this, you should have references to all the branches from that remote, which you can merge in or inspect at any time. If you clone a repository, the command automatically adds that remote repository under the name “origin”. So, git fetch origin fetches any new work that has been pushed to that server since you cloned (or last fetched from) it. It’s important to note that the git fetch command only downloads the data to your local repository — it doesn’t automatically merge it with any of your work or modify what you’re currently working on. You have to merge it manually into your work when you’re ready. If your current branch is set up to track a remote branch (see the next section and Git Branching for more information), you can use the git pull command to automatically fetch and then merge that remote branch into your current branch. This may be an easier or more comfortable workflow for you; and by default, the git clone command automatically sets up your local master branch to track the remote master branch (or whatever the default branch is called) on the server you cloned from. Running git pull generally fetches data from the server you originally cloned from and automatically tries to merge it into the code you’re currently working on. Note From git version 2.27 onward, git pull will give a warning if the pull.rebase variable is not set. Git will keep warning you until you set the variable. If you want the default behavior of git (fast-forward if possible, else create a merge commit): git config --global pull.rebase "false" If you want to rebase when pulling: git config --global pull.rebase "true" Pushing to Your Remotes When you have your project at a point that you want to share, you have to push it upstream. The command for this is simple: git push <remote> <branch> . If you want to push your master branch to your origin server (again, cloning generally sets up both of those names for you automatically), then you can run this to push any commits you’ve done back up to the server: $ git push origin master This command works only if you cloned from a server to which you have write access and if nobody has pushed in the meantime. If you and someone else clone at the same time and they push upstream and then you push upstream, your push will rightly be rejected. You’ll have to fetch their work first and incorporate it into yours before you’ll be allowed to push. See Git Branching for more detailed information on how to push to remote servers. Inspecting a Remote If you want to see more information about a particular remote, you can use the git remote show <remote> command. If you run this command with a particular shortname, such as origin , you get something like this: $ git remote show origin * remote origin Fetch URL: https://github.com/schacon/ticgit Push URL: https://github.com/schacon/ticgit HEAD branch: master Remote branches: master tracked dev-branch tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) It lists the URL for the remote repository as well as the tracking branch information. The command helpfully tells you that if you’re on the master branch and you run git pull , it will automatically merge the remote’s master branch into the local one after it has been fetched. It also lists all the remote references it has pulled down. That is a simple example you’re likely to encounter. When you’re using Git more heavily, however, you may see much more information from git remote show : $ git remote show origin * remote origin URL: https://github.com/my-org/complex-project Fetch URL: https://github.com/my-org/complex-project Push URL: https://github.com/my-org/complex-project HEAD branch: master Remote branches: master tracked dev-branch tracked markdown-strip tracked issue-43 new (next fetch will store in remotes/origin) issue-45 new (next fetch will store in remotes/origin) refs/remotes/origin/issue-11 stale (use 'git remote prune' to remove) Local branches configured for 'git pull': dev-branch merges with remote dev-branch master merges with remote master Local refs configured for 'git push': dev-branch pushes to dev-branch (up to date) markdown-strip pushes to markdown-strip (up to date) master pushes to master (up to date) This command shows which branch is automatically pushed to when you run git push while on certain branches. It also shows you which remote branches on the server you don’t yet have, which remote branches you have that have been removed from the server, and multiple local branches that are able to merge automatically with their remote-tracking branch when you run git pull . Renaming and Removing Remotes You can run git remote rename to change a remote’s shortname. For instance, if you want to rename pb to paul , you can do so with git remote rename : $ git remote rename pb paul $ git remote origin paul It’s worth mentioning that this changes all your remote-tracking branch names, too. What used to be referenced at pb/master is now at paul/master . If you want to remove a remote for some reason — you’ve moved the server or are no longer using a particular mirror, or perhaps a contributor isn’t contributing anymore — you can either use git remote remove or git remote rm : $ git remote remove paul $ git remote origin Once you delete the reference to a remote this way, all remote-tracking branches and configuration settings associated with that remote are also deleted. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://git-scm.com/book/zh-tw/v2/Git-%e5%9f%ba%e7%a4%8e-%e8%88%87%e9%81%a0%e7%ab%af%e5%8d%94%e5%90%8c%e5%b7%a5%e4%bd%9c | Git - 與遠端協同工作 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.5 Git 基礎 - 與遠端協同工作 與遠端協同工作 為了能在任意的 Git 專案上協同工作，你需要知道如何管理你的遠端版本庫。 遠端版本庫是指被託管在網際網路或其他網路中的各種專案版本庫。 你可以擁有許多遠端版本庫；通常來說，它如果不是唯讀的，就是可讀寫的。 與其它人協同工作包括了：「管理」遠端版本庫、以及將分享的資料「推送（push）」到端遠版本庫、或者從遠端版本庫「拉取（pull）」分享的資料： 管理遠端版本庫則包括了了解如何：「新增」遠端版本庫、「移除」不再有效的遠端版本庫、管理各式各樣的「遠端分支」、定義遠端分支是否被「追蹤」等等。 我們將在這一節介紹這些遠端管理技巧。 顯示你的遠端 使用 git remote 命令可以檢視你已經設定好的遠端版本庫， 它會列出每個遠端版本庫的「簡稱」。 如果你克隆（clone）了一個遠端版本庫，你至少看得到「origin」——它是 Git 給定的預設簡稱，用來代表被克隆的來源。 $ git clone https://github.com/schacon/ticgit Cloning into 'ticgit'... remote: Reusing existing pack: 1857, done. remote: Total 1857 (delta 0), reused 0 (delta 0) Receiving objects: 100% (1857/1857), 374.35 KiB | 268.00 KiB/s, done. Resolving deltas: 100% (772/772), done. Checking connectivity... done. $ cd ticgit $ git remote origin 你也可以指定 -v 選項來顯示 Git 用來讀寫遠端簡稱時所用的網址。 $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) 如果遠端版本庫不止一個，這個命令會將它們全部列出來。 例如，一個版本庫內連結了許多其它協作者的遠端版本庫，可能看起來就像這樣： $ cd grit $ git remote -v bakkdoor https://github.com/bakkdoor/grit (fetch) bakkdoor https://github.com/bakkdoor/grit (push) cho45 https://github.com/cho45/grit (fetch) cho45 https://github.com/cho45/grit (push) defunkt https://github.com/defunkt/grit (fetch) defunkt https://github.com/defunkt/grit (push) koke git://github.com/koke/grit.git (fetch) koke git://github.com/koke/grit.git (push) origin git@github.com:mojombo/grit.git (fetch) origin git@github.com:mojombo/grit.git (push) 這意味著我們可以很輕鬆地拉取任何協作者的貢獻； 我們可能對其中某些遠端版本庫還擁有推送權限，不過我們不會在這裡詳述這個部分。 注意：這些遠端版本庫使用了不同的通訊協定；我們將會在 在伺服器上佈署 Git 對它有更多的說明。 新增遠端版本庫 我們在之前的章節中已經提過並給了一些範例來說明 clone 命令如何隱式地為你加入 origin 遠端； 而在這裡將說明如何「明確地」新增一個遠端。 選一個你可以輕鬆引用的簡稱，用來代表要新增的遠端 Git 版本庫，然後執行 git remote add <簡稱> <url> 來新增它： $ git remote origin $ git remote add pb https://github.com/paulboone/ticgit $ git remote -v origin https://github.com/schacon/ticgit (fetch) origin https://github.com/schacon/ticgit (push) pb https://github.com/paulboone/ticgit (fetch) pb https://github.com/paulboone/ticgit (push) 現在你可以在命令列中使用 pb 這個字串來代表整個網址； 例如，如果你想從 Paul 的版本庫中取得所有資訊，而這些資訊並不存在於你的版本庫中，你可以執行 git fetch pb ： $ git fetch pb remote: Counting objects: 43, done. remote: Compressing objects: 100% (36/36), done. remote: Total 43 (delta 10), reused 31 (delta 5) Unpacking objects: 100% (43/43), done. From https://github.com/paulboone/ticgit * [new branch] master -> pb/master * [new branch] ticgit -> pb/ticgit 現在 Paul 的 master 分支可以在本地端透過 pb/master 存取到（譯註：把 pb/master 想成 Paul 的 master 在你本地端的「分身」——實際上它被稱為「遠端追蹤分支（remote-tracking branch）」）——你可以把它合併（merge）到你的其中一個分支；或者，如果你想要檢視它的話，可以在它身上檢出（checkout）一個本地分支。 （我們將會在 [ch03-git-branching] 中詳細介紹什麼是分支以及如何使用它們。） 從你的遠端獲取或拉取 如同你剛剛所看到的，要從你的遠端專案中取得資料，你可以執行： $ git fetch [remote-name] 這個命令會連到遠端專案，然後從遠端專案中將你還沒有的資料全部拉下來； 執行完成後，你應該會有那個遠端版本庫中所有分支的參照（reference）（譯註：再次強調，遠端的分支在本地端的分身——遠端追蹤分支），可以隨時用來合併或檢視。 如果你克隆了一個版本庫， clone 命令會自動增加一個「origin」來代表遠端版本庫； 所以， git fetch origin 會獲取（fetch）在你克隆（或者最後一次獲取）之後任何被推送到伺服器上的新的工作內容。 很重要的一點是： git fetch 命令只會下載資料到你的版本庫——它並不會自動合併你的任何工作內容，也不會自動修改你正在修改的東西； 當你準備好合併你的工作內容時，你必需用手動的方式進行合併。 如果你的目前分支被設定為「追蹤」遠端上的分支（閱讀下一節以及 [ch03-git-branching] 以了解更多資訊），你便可使用 git pull 命令來自動「獲取」並「合併」那個遠端分支到你目前的分支裡去； 由於 git clone 命令會「自動地」將本地分支 master 設定為「追蹤」遠端上的 master（無論預設分支叫什麼名稱。譯註：只要是預設分支都會自動設定追踨行為，而 master 常常是預設分支），這可能會讓你有比較輕鬆自在的工作流程： 只要執行 git pull 通常就會從你最初克隆的伺服器上獲取資料，然後試著自動合併到目前的分支。 推送到你的遠端 當你想分享你的專案成果時，你必需將它推送到上游。 推送的命令很簡單： git push [remote-name] [branch-name] 。 如果你想要將 master 分支推送到 origin 伺服器上時（再次說明，克隆時通常會自動地幫你設定好 master 和 origin 這二個名稱），那麼你可以執行這個命今將所有你完成的提交（commit）推送回伺服器上。 $ git push origin master 只有在你對克隆來源的伺服器有寫入權限，並且在這個當下還沒有其它人推送過，這個命令才會成功； 如果你和其它人同時做了克隆，然後他們先推送到上游，接著換你推送到上游，毫無疑問地你的推送會被拒絕； 你必需先獲取他們的工作內容，將其整併到你之前的工作內容，如此你才會被允許推送。 閱讀 [ch03-git-branching] 以了解更多關於「如何推送到遠端伺服器」的詳細資訊。 檢視遠端 如果你想要對一個特定遠端檢視更多資訊，你可以使用 git remote show [remote-name] 命令。 如果你在執行這個命令中使用特定的簡稱，例如 origin ，你會得到下面這個類似的訊息： $ git remote show origin * remote origin Fetch URL: https://github.com/schacon/ticgit Push URL: https://github.com/schacon/ticgit HEAD branch: master Remote branches: master tracked dev-branch tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) 它同時列出了遠端版本庫的網址和「追蹤分支（tracking branch）」資訊。 這個命令很有用地告訴你：目前分支是 master（譯注：HEAD 意味著目前的），如果你執行 git pull ，它會在獲取所有遠端參照之後，自動將遠端的 master 合併到你的 master 分支。 它也會列出所有已抓下來的遠端參照（譯註：此例中指「master tracked」和「dev-branch tracked」）。 這是一個你很可能會遇到的簡單例子； 然而，當你更重度地使用 Git 後，你將會從 git remote show 中看到更多的資訊： $ git remote show origin * remote origin URL: https://github.com/my-org/complex-project Fetch URL: https://github.com/my-org/complex-project Push URL: https://github.com/my-org/complex-project HEAD branch: master Remote branches: master tracked dev-branch tracked markdown-strip tracked issue-43 new (next fetch will store in remotes/origin) issue-45 new (next fetch will store in remotes/origin) refs/remotes/origin/issue-11 stale (use 'git remote prune' to remove) Local branches configured for 'git pull': dev-branch merges with remote dev-branch master merges with remote master Local refs configured for 'git push': dev-branch pushes to dev-branch (up to date) markdown-strip pushes to markdown-strip (up to date) master pushes to master (up to date) 這個命令顯示了當你在特定的分支上執行 git push 時，它將自動推送到哪一個遠端分支； 它也顯示了：哪些遠端分支是在你的本地端還沒有的（譯註：new 屬性）、哪些你曾獲取過的遠端分支已經在遠端上被移除了（譯註：stale 屬性）、哪些本地分支是有能力在執行 git pull 後自動和它們的遠端追蹤分支合併。 移除或重新命名遠端 你可以執行 git remote rename 來重新命名遠端的簡稱。 例如：如果你想要將 pb 重新命名為 paul ，你可以這樣使用 git remote rename ： $ git remote rename pb paul $ git remote origin paul 值得一提的是：它會更新所有遠端追蹤分支的名稱； 曾經用來被參考的遠端追蹤分支 pb/master 現在改名為 paul/master 。 如果你因為某些原因想要移除一個遠端——你搬動了伺服器、或者不再使用某個特定的鏡像、或者某個貢獻者不再貢獻了——你可以執行 git remote rm ： $ git remote rm paul $ git remote origin prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://www.atlassian.com/zh/software/jira/free?templateId=com.pyxis.greenhopper.jira:gh-cross-team-template | Jira Free：免费获取 Jira Software | Atlassian Close 是否使用 您的语言 查看此页面？ 所有语言 选择您的语言 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski | 2026-01-13T09:29:41 |
https://ftp.gnu.org/old-gnu/gnotary/?C=D;O=A | Index of /old-gnu/gnotary Index of /old-gnu/gnotary Name Last modified Size Description Parent Directory - client/ 2005-08-17 17:58 - Apache/2.4.52 (Trisquel_GNU/Linux) Server at ftp.gnu.org Port 443 | 2026-01-13T09:29:41 |
https://www.microsoft.com/ko-kr/ai/financial-services/insurance | 보험 산업의 디지털 혁신 | Microsoft AI This is the Trace Id: 62fbf3cf8de88537950fe226fd66947a 주 콘텐츠로 건너뛰기 Microsoft Microsoft AI Microsoft AI Microsoft AI 홈 제품 및 솔루션 조직용 조직용 Microsoft 365 Copilot Microsoft 365 Copilot 앱 다운로드 조직용 Copilot Agent 365 Customize your Copilot Customize your Copilot Copilot Studio Build your own Build your own Microsoft Foundry Foundry Tools Azure AI 솔루션 파트너 제공 파트너 제공 Microsoft Marketplace Intelligent PCs Intelligent PCs Copilot+ PCs 개인용 개인용 Microsoft Copilot Copilot 앱 다운로드 업계 솔루션 소비재 보안 및 인텔리전스 교육 에너지 및 자원 에너지 및 자원 개요 전력 및 유틸리티 석유 및 가스 채광 금융 서비스 금융 서비스 개요 뱅킹 자본 시장 보험 정부 기관 정부 기관 개요 대중교통 및 도시 인프라 공공 금융 공중 보건 및 복지 서비스 공공 안전 및 정의 의료 서비스 및 생명 과학 의료 서비스 및 생명 과학 개요 공급자 Payors 생명과학 제조 제조 개요 산업 혁신 미디어 및 엔터테인먼트 이동성 이동성 개요 자동차 여행 및 교통 소매 통신 비즈니스 리더를 위한 AI AI 사용 사례 신뢰할 수 있는 AI 책임 있는 AI 책임 있는 AI Microsoft 책임 있는 AI 원칙 및 접근 방식 도구 및 사용 지속 가능성 지속 가능성 지속 가능성 강화 보안 유지 보안 유지 AI 보안 강화 데이터 보호 및 개인 정보 알아보기 AI 101 AI 학습 허브 업계 블로그 Microsoft Cloud 블로그 지원 비즈니스 고객을 위한 지원 산업 문서 자세히 산업 Insurance</h1> "> 보험 AI 시대에 비즈니스 가치를 실현하고 고객 관계를 강화하세요. 비디오 보기 전자책 읽기 개요 개요 시나리오 고객 사례 파트너 제품 리소스 개요 Microsoft for Financial Services</h2> "> 금융 서비스용 Microsoft 데이터와 AI를 통해 보험 계약자 환경을 개선하고, 협업을 향상하고, 영향력 있는 비즈니스 성과를 이끌어냅니다. 보험 계약자 환경 혁신 심층적인 인사이트와 관계를 통해 차별화된 보험 계약자 환경을 제공합니다. 보험 직원 및 에이전트 역량 강화 더 나은 팀워크, 인사이트, 커뮤니케이션을 통해 생산성을 향상시킵니다. 위험 및 규정 준수 관리 위험 모델링을 개선하고, 규정 준수를 용이하게 하며, 사기로부터 보호합니다. 핵심 보험 운영 현대화 클라우드의 주요 프로세스를 혁신하여 신제품을 빠르게 출시합니다. 지속 가능한 미래 만들기 ESG 솔루션과 분석을 통해 금융 서비스에서 영향력 있는 지속 가능성 성과를 이끌어냅니다. 시나리오 Explore use cases</h2> "> 사용 사례 살펴보기 보험 기술 솔루션이 비즈니스 가치를 실현하고 고객 관계를 강화하는 방법을 알아봅니다. 보험 계약자 환경 혁신 직원 및 에이전트 역량 강화 위험 및 규정 준수 관리 핵심 운영 현대화 이전 다음 고객 참여 개인 설정된 AI 증강 고객 환경을 통해 문제 해결 시간을 단축하고 지갑 점유율을 늘리세요. 고객 인사이트 전체적인 고객 보기를 위해 서로 다른 데이터 원본을 통합하고 실시간 인사이트와 적극적인 참여를 지원합니다. 증강 인텔리전스 강력한 AI 도구와 기능을 사용하여 모든 디지털 채널에서 고객 환경을 개인 설정하고 증강합니다. 연락 센터 현대화 고객 상호 작용을 개인 설정하고 보호하면서 옴니채널 참여와 지능형 셀프 서비스를 지원합니다. 직원 및 에이전트 생산성 적절한 도구, 데이터, 인사이트를 통해 효율성을 개선하고 인력의 역량을 강화합니다. 그룹 간 협업 부서 간 협업을 간소화하고 주요 리소스 및 도구에 대한 액세스를 중앙 집중화합니다. 실시간 커뮤니케이션 최신 커뮤니케이션 도구 모음을 통해 실시간 참여 및 라이브 이벤트를 지원합니다. 직원 경험 데이터 기반 인사이트를 통해 일과 삶의 통합을 최적화하여 포용과 웰빙을 촉진합니다. 보험 통계 위험 더 빠른 모델링 및 심층적인 위험 인사이트를 통해 보험 통계 생산성을 개선합니다. 비상 재해 위험 위험한 상태의 보험 자산과 관련된 인사이트를 향상시키고 실시간 데이터 분석 및 인사이트를 제공합니다. 재무 위험 재무 예측 및 인사이트를 발전시키고, 적립 및 자본 관리를 향상하고, 규제 보고를 개선합니다. 사이버 보안 및 사기 방지 클레임 및 인수 사기로부터 보호하고 진짜 클레임을 더 빠르게 처리합니다. 핵심 시스템 마이그레이션 클라우드로 이동하여 비용을 절감하고, 처리 시간을 향상하고, 부가 가치 클라우드 서비스에 액세스합니다. 인수 현대화 인수 비용을 절감하고, 견적 속도를 개선하고, 고객 환경을 향상합니다. 클레임 현대화 문제 해결 시간을 단축하고, 비용을 절감하고, AI를 사용하여 클레임 프로세스를 간소화하고, 고객 환경을 개선합니다. 탭으로 돌아가기 보안 및 규정 준수 Build on a trusted cloud</h2> "> 신뢰할 수 있는 클라우드에 구축 인텔리전스, 보안, 규정 준수를 기반으로 위험을 완화하고 비즈니스 가치를 실현하세요. 다음을 수행할 수 있습니다. 규정 준수 요구 사항을 충족합니다. 보안 및 개인 정보 보호 강화 복원력 및 투명성을 강화합니다. 자세한 정보 고객 사례 See how insurers are innovating</h2> "> 혁신하고 있는 보험 회사 사례 보기 이전 슬라이드 다음 슬라이드 “Dynamics 365 Marketing에서 즉시 알아차린 한 가지는 훨씬 더 현대적이라는 것입니다.” Carolin Kräling, 제품 소유자 40% 잠재 고객 품질 향상 제품 Dynamics 365 Power Apps 사례 읽기 “저희는 IT 팀이나 개발자에게 접근할 수 없는 내부 고객이 직접 봇을 빌드할 수 있는 솔루션을 원했습니다.” Roger Reese, IT DevOps 엔지니어 책임자 50,000 잠재적인 내부 사용자 제품 Microsoft Entra ID Power Automate 사례 읽기 “저희는 가능한 모든 기술 파트너와 상의했습니다. Microsoft가 우리의 가치와 가장 일치하고 보완적이었습니다.” Cristiano Gianni, Health Beyond Insurance 책임자 170만 고유 사용자 제품 Azure Synapse Analytics Power BI 사례 읽기 “Azure Machine Learning을 사용하여 사기를 사전에 해결하는 기능은 엄청난 잠재력을 가지고 있습니다.” Aaron Minkovich, 최고 기술 책임자 50% 비용 절감 제품 Foundry Tools Azure Machine Learning 사례 읽기 고객 사례 캐러셀로 돌아가기 파트너 솔루션 Explore insurance solutions</h2> "> 보험 솔루션 살펴보기 Microsoft 파트너 에코시스템에서 보험 및 제품을 살펴보세요. 솔루션 살펴보기 이전 슬라이드 다음 슬라이드 Duck Creek Technologies</h3> "> 핵심 작업 Duck Creek Technologies 손해 보험 및 일반 보험 산업을 위한 핵심 시스템 솔루션을 살펴보세요. 자세한 정보 Shift Claims Fraud Detection</h3> "> 사기 검색 교대 근무 클레임 사기 검색 손해 보험 회사를 위한 AI 기반 사기 솔루션을 배포합니다. 자세한 정보 Milliman Integrate</h3> "> 보험 통계 및 위험 Milliman Integrate 보험 통계 및 위험 보고를 위한 최초로 완전히 산업화된 솔루션을 살펴보세요. 자세한 정보 Majesco Copilot</h3> "> AI 지원 Majesco Copilot 정책, 청구, 클레임, 인수, 손실 제어에 생성형 AI를 적용합니다. 자세한 정보 Willis Towers Watson RiskAgility FM Cloud</h3> "> 보험 통계 위험 Willis Towers Watson RiskAgility FM Cloud 보험 통계 모델링을 위해 클라우드에서 데이터 및 소프트웨어를 안전하게 호스트하고, 관리하고, 실행합니다. 자세한 정보 Avanade Entra Verified ID Consulting</h3> "> ID 및 액세스 Avanade Entra 확인된 ID 컨설팅 Microsoft 365, Active Directory 등과 같은 기존 Azure 서비스에 탈중앙화 ID를 포함합니다. 자세한 정보 PwC Customer Link</h3> "> 고객 프로필 PwC 고객 링크 개인화되고 실시간으로 작동하는 옴니채널 고객 참여를 구축하고 활성화하세요. 자세한 정보 HSO’s CRM Accelerator for Financial Services</h3> "> 고객 참여 금융 서비스를 위한 HSO의 CRM 가속기 간소화된 운영 및 개인 설정된 고객 참여를 지원합니다. 자세한 정보 FRISS Claims Analytics</h3> "> 클레임 분석 FRISS 클레임 분석 자동화된 사기 검색을 통해 가양성을 줄이고 실시간으로 클레임 점수를 매깁니다. 자세한 정보 파트너 솔루션 섹션으로 돌아가기 제품 Discover Microsoft products</h2> "> Microsoft 제품 살펴보기 매우 안전하며 규정을 준수하는 플랫폼인 Microsoft Cloud를 기반으로 구축된 제품과 솔루션을 살펴보세요. 이전 슬라이드 다음 슬라이드 Microsoft Azure Azure를 사용하여 혁신적인 보험용 클라우드 솔루션을 만드세요. 자세한 정보 Microsoft Fabric AI 기반 단일 플랫폼을 사용하여 조직의 모든 사람이 데이터에 액세스하고, 관리하고, 사용하는 방식을 재구성하세요. 자세한 정보 Microsoft Power Platform 로우 코드 도구를 사용하여 비용 및 개발 시간을 단축하세요. 자세한 정보 Microsoft 365 보험용 Microsoft 365 솔루션을 사용하여 작업 공간 현대화를 촉진하고 위험 노출을 줄입니다. 자세한 정보 Microsoft Teams 최전방 직원을 위한 매우 안전한 도구를 사용하여 커뮤니케이션, 협업, 운영을 향상시킵니다. 자세한 정보 Microsoft 365 Copilot Microsoft 365 Copilot을 사용하여 생산성을 높이고 효율성을 높이고 비즈니스 결과를 개선하세요. 자세한 정보 Microsoft Dynamics 365 팀, 프로세스, 데이터를 연결하여 뛰어난 고객 환경과 운영 민첩성을 제공합니다. 자세한 정보 Microsoft Security 플랫폼과 클라우드 환경에서 작동하는 비즈니스 보안 솔루션으로 조직을 보호하세요. 자세한 정보 구입 섹션으로 이동 Meet compliance requirements</h2> "> 규정 준수 요구 사항 충족 DORA(Digital Operational Resilience ACT)를 지원하기 위한 Microsoft의 약속에 대해 알아봅니다. 자세한 정보 Discover valuable resources</h2> "> 유용한 리소스 살펴보기 Secure and Compliant Innovation in Insurance with AI</h3> "> 인포그래픽 • 2025년 4월 AI를 활용한 안전하고 규정을 준수하는 보험 혁신 IDC의 인포그래픽에서 AI 기반 혁신으로 보험사를 강화하는 방법을 알아보세요. 인포그래픽 받기 4 ways Microsoft Copilot empowers financial services employees</h3> "> 블로그 Microsoft Copilot이 금융 서비스 직원을 지원하는 4가지 방법 블로그 읽기 Social inflation is costing insurers—here's how cloud and AI can help</h3> "> 블로그 소셜 인플레이션이 보험사에 비용을 발생시키고 있습니다. 클라우드와 AI가 어떻게 도움이 되는지 알아보세요. 블로그 읽기 The future of insurance in the era of AI</h3> "> 전자책 AI 시대 보험의 미래 전자책 받기 다음 단계 Start achieving more in insurance</h2> "> 보험 분야에서 더 많은 성과 달성 책임 있는 AI Microsoft AI 원칙 및 관행 Microsoft가 거버넌스, 정책, 연구를 통해 책임 있는 AI 관행을 위해 계속 노력하는 방법을 살펴보세요. 책임 있는 AI 살펴보기 규정 준수 Microsoft 클라우드용 준수 프로그램 주제 특화 전문가와 소통하여 위험, 감사, 규정 준수 팀을 지원하고 클라우드 채택을 가속화하세요. 자세한 정보 설명서 금융 서비스용 Microsoft 설명서 읽기 온라인 교육, 방법 문서 및 기타 리소스를 사용하여 금융 서비스를 위한 Microsoft를 최대한 활용하는 방법을 알아봅니다. 지금 살펴보기 규정 준수 문서 를 읽고 보안 센터 를 방문하여 금융 서비스 규정 준수, 데이터 보호 및 개인 정보 보호에 대한 Microsoft의 약속에 대해 자세히 알아보세요. 여기에서 DORA 규정 준수에 대해 여기 에서 자세히 알아보세요. 팔로우하기 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 | 2026-01-13T09:29:41 |
https://www.linkedin.com/uas/login?fromSignIn=true&session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fcoachhub&trk=organization_guest_main-feed-card_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=POST&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:41 |
https://www.drupal.org/docs/contributed-modules/configuration-kits#search-block-form | Configuration Kits | Contributed module documentation | Drupal Wiki guide on Drupal.org Skip to main content Skip to search Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see ? Yes, please No, do not track me Drupal.org home Discover Drupal Drupal Core Drupal CMS Drupal AI Case Studies Drupal for Government Drupal for Higher Education Drupal for Nonprofit Drupal for eCommerce Drupal for FinTech Drupal for Healthcare Drupal for Enterprise Drupal for Retail Drupal for Travel & Tourism Build with Drupal Download Drupal Documentation Getting started Local Development Guide Developer Resources Drupal CMS User Guide Drupal User Guide API Modules Themes Distributions Issue queues Security Advisories Partners & Services Find a Drupal Certified Partner Become a Drupal Certified Partner Find a Hosting Provider Find a Migration Partner Find Training Drupal Steward Community About the Community How to Contribute DrupalCon Events Jobs / Careers News & Blogs Forum Slack Newsletters Drupal Swag Shop Support Drupal The Drupal Association Donate Become a Partner Become a Ripple Maker Become an Organization Member Drupal Swag Shop Get Started Try Drupal CMS Try Hosting Return to content Search form Search Log in Create account Documentation Search Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options. Migration Resource Center Drupal Extending Drupal Contributed modules Contributed module documentation Advertising sustains the DA. Ads are hidden for members. Join today Contributed module documentation Active Tags A11Y Paragraphs Tabs AI AI Interpolator AI Migration API Authentication API module APITools Accelerated Mobile Pages (AMP) Access NASA API Access Policy Accessibility Scanner Acquia Migrate: Accelerate Actions UI Activity Tracker module ActivityPub Add To Calendar Date Augmenter AddToAny Share Buttons Address Decoupled Address for Luxembourg Address for Rep. of Moldova Admin Menu Swap Adobe Launch Advanced CSS/JS Aggregation Advanced Email Validation Advanced File Destination - Ho to use Advanced Insert View Advanced Varnish Advanced Views RSS Feed Aggregator Akamai Album Photos Alexa Allow a content type only once (Only One) Altcha Anu LMS Apigee API Catalog Apigee Developer Portal Kickstart Apigee Edge Apigee Monetization Apple News Astrology Atoms AudioField Audit files Augmentor User Guide Authorization Auto Link Auto Node Translate Auto Taxonomy Term Translate AutoFloat Automatic Updates Avatar Kit Azure Drupal Sync BAT Guide BEE hotel Backstop Generator Backup and Migrate Bamboo Twig Barcodes Behat UI Better Exposed Filters Bibliography & Citation BigCommerce Block Class Block Form Alter Block List Override Block Style Plugins Blog Book Boost Bootstrap Layouts Bootstrap Paragraphs Bootstrap Quick Tabs Bootstrap Theme Toggler Block Bothive Chatbot Botman Boxout Braintree Cashier Breakgen Brightcove Video Connect Bundle override Burndown Business Rules Bynder CAS CDEK API CKEditor 4 LTS CKEditor 5 Premium Features CKEditor CKEditor Accessibility Auditor CKEditor CodeMirror CKEditor Entity Link CKEditor Font Size and Family CKEditor Google Search CKEditor Libraries Group CKEditor: N1ED plugin CMRF Core Documentation CSV Importer CSV to Config Cached moderation state Calendar View Canvas LTI Captcha Keypad Changed Fields API (8.x-3.x) Changed Fields API Chaos Tool Suite (ctools) Chart Suite Guide Charts Chatbot API Chatbot Framework Claro Cloud Cloudflare Stream Cloudinary Coder Collapsiblock Color Color Field Comment Notify Comment mover Commerce Commerce API Commerce Affirm Credit Payment Gateway Commerce Approve Commerce Authorize.Net Commerce Braintree Commerce Cart API Commerce Cart Flyout Commerce DIBS integration Commerce Easy Commerce Funds Commerce Google Tag Manager Commerce Ingenico Commerce Inventory Commerce Invoice Commerce Migrate Commerce NoFraud Commerce Order Document Commerce PVT Commerce Pagseguro Transparente Commerce PayPal Commerce Payment Extra Commerce Point of Sale (POS) Commerce PostFinance Checkout Commerce Postfinance Commerce Product Options Commerce Recurring Metered Commerce Rental Commerce Reporting Commerce Square Connect Commerce Time Slots Commerce Tpay Commerce TrustedShops Commerce Variation Add-on Commerce Webform Order Commerce iATS Commerce iDEAL Payment Gateway Component Schema Components Computed Field Computed Field Plugin Conditional Fields Config Override Inspector Config Pages Config Single Export Config Token Config partial export Configuration Kits Configuration Split Content Alerts Content Feedback Content Import Content Packager Content Planner Content Synchronization Content-Security-Policy ContentAccess Create fields programmatically Crossword CrowdSec CsvtoTable Cura Childcare Suite Cura Childcare Suite Currency Custom 4XX Pages Custom API Custom Field Custom Status Report Custom Tokens Custom Tokens and its snippets Custom breadcrumbs Customerror D8 Rules Essentials Dashboard Date Augmenter API Decoupled Blocks: Vue.js Decoupled Toolbox Decoupled Toolbox Decoupled quiz Default Content for D8 Delete Entity Translations Dempo Deploy Deploying Meilisearch to production Devel Devel Generate Commerce Developer Suite Developer portal Digital Signage Framework Disclosure Menu Disclosure Menu Display Suite Chained Fields Dominican Catalogus Module DraggableViews Drupal Chatbot Drupal Commerce Merchant Warrior Drupal Contribution Drupal Diversity & Inclusion Drupal Js Path Drupal LMS Drupal OAuth & OpenID Connect Login - OAuth2 Client SSO Login Drupal OAuth OIDC Login Drupal Remote Dashboard Drupal Slider Drupal Website Security – Complete Protection for Your Site Drupal WhatsApp Drupal YouTuber Drupal driver for SQL Server and SQL Azure DubBot ECA: Event - Condition - Action ECC EU Cookie Compliance EVA Easy Breadcrumb Easy News Editor Button Link Ek Jitsi Elasticsearch Connector Email Verification / SMS Verification / OTP Verification Encrypt Entitree Administration Guide Entity Access Password Entity Browser - Table Layout Entity Browser Entity Pager Entity Parser Entity Prepopulate Entity Print Entity Reference Facet Link Entity Reference Override Entity Reference Views Entity Reference Views Select Entity Registration Entity Search Autoindex Entity Share Entity Share WebSub Entity Update Entity Usage Entity Usage Addons Entity browser Environment indicator Epsilon Harmony Connector Ethereum Evaluate Webform Event Platform Events Logger Excel Importer Exerciser Usage Expire reset password link Extensions API External Authentication External Entities External Entities Database storage Extra Block Types (EBT) Extra Paragraph Types (EPT) Facebook Instant Articles Facet Bot Blocker Facets Facets Date Range Picker Factory Lollipop Feature Toggle Features Feeds Feeds Migrate Feeds Paragraphs Feeds extensible parsers Field Encrypt Field Gallery Field Group Field Inheritance Field description tooltip Field validation File Extractor Filebrowser FillPDF Firebase Authentication Guide Fivestar Flag Flag Lists Flashpoint Education Flexible Views Flickr Integration Suite Flow2 Fluent Flysystem Focal Point Focal Point FolderShare Guide Font Awesome Icons Footnotes Form mode manager FormAlter as Plugin FormAssembly Formatter Suite Guide Formdazzle! Forms steps FortyTwo Forum module Forward Freelinking Frontend Editing Frontify Assets FullCalendar Block Funding GA Push GIT Info Report GLightbox Gatsby Integration General Data Protection Regulation Geocluster D8/D9 Set-up Geofield Geolocation Field Get Linkedin Posts Ghost Inspector Integrator Ghost Inspector Integrator Gin Toolbar Custom Menu Ginger Robot Gardens Ginger Robot Suite Give GlobalDoc’s LangXpert Connect for Drupal Googalytics Google API PHP Client Google Analytics Google Analytics Counter Google Analytics Search API Autocomplete Google Authentication for Users Google Bard Google Calendar Import Google Programmable Search Engine Gophish Integration GovUK Notify GrapesJs Editor - Page builder GraphQL Grid Widget Group Group Content Moderation Group Flex Group Invite Group Media Group Subscription Group by Field Widget Grouper Usage Gutenberg Gutenberg Content Embed Gutenberg Starter Gutenberg Starter Gutenberg USWDS Guzzle REST Generator HAL HAX HTML Mail HTML Title HTTP Client Manager Hanging Conjunctions Filter HelloSign Hidden Tab Honeypot Hospital Price Transparency Hotkeys for Save How to Configure Drupal Sharepoint Integration How to test a module locally using DDEV (Webform Booking example) Human Presence Form Protection Hux IMCE File Manager IPMA Weather Iconify Icons If Then Else Iframe Media Embed Video Image Base64 Formatter Image Optimize Image Replace Imageshop Immoweb API Client In Other Words Inline Formatter Field Insert Instagram Block Integrating Frontify with Drupal: A Comprehensive Guide Intercept Islandora JSON Field Utils JSON:API Search API Janrain Connect Juicebox HTML5 Responsive Image Galleries Juicer - Social Media Feed Aggregator Key Keycloak OpenID Connect Klaro Consent Management Knowledge Konami Code LDAP Integration LDAP Integration with Active Directory and OpenLDAP - NTLM & Kerberos Login Language Negotiation Url Matrix Layout BG Layout Builder Additions Layout Builder Block Sanitizer Layout Builder Plus Layout Builder Restrictions Layout Builder Settings Report Layout Builder Styles Layout Builder Tabs Section Layout Components Layout Options Layout Paragraphs Lazy-load Leaflet Leaflet More Markers Libraries API LiftIgniter Lightgallery Lightning Accessibility Lightweight Directory Access Protocol (LDAP) Link attributes Link icon Linkback Linkit Lndr Localist Drupal Localization server Localized Configuration Loco Translate Loqate Ludwig Lunr search Maestro Maestro Activepieces Integration Mailchimp Maintenance Manage display Managing User Account Expiration with User Expire Module Mapbox Field Markdown Markdown Easy Markdown Exporter Marketing Cloud Mask Field Matomo Analytics Maxlength Media Contextual Crop Media Gallery Media Library Form Element Media PDF Thumbnail Media Video Micromodal Media: Acquia DAM Membership Menu Manipulator Menu Migration (Import & Export) Message Message Integration Message Thread Metatag Metatag Google Scholar Micro Site Microsoft Entra ID SSO Login Microsoft Entra sync Migrate Magician Migrate QA Migrate Source CSV Migrate Source GraphQL Migrate Source JCR Migration Tools Mime Mail Mix Modal Modifiers Moodle REST Mother May I Multilanguage Form Display Multiple Registration Multistep Form Framework Multiversion NASA Astronomy Picture of the Day NFT Name Field Nbox Node Type count Notify OAuth 1.0 OAuth Server - API Documentation OAuth Server - SSO Setup Guides OAuth2 & OpenID Connect OAuth2 Client OEmbed Lazyload OH Office 365 Connector One Time Password SMS Open ReadSpeaker OpenChurch OpenEDU OpenID Connect OpenID Connect Microsoft Azure Active Directory client OpenLayersD8 OpenQuestions Openlayers Oracle Driver Oracle Eloqua API Redux OwnTracks PCO - Planning Center Online API PHP filter PNX Gallery PNX Media Packages Packagist Pagedesigner Panopoly 2 for Drupal 8/9 Paragraph Group Paragraphs Paragraphs Bundles Paragraphs Bundles Import Paragraphs Collection Paragraphs Gridstack Paragraphs Role Visibility Parameter Message Paranoia Pathauto Patternkit Performance Budget Permalink Block Permanent Entities Permissions by Term Persistent Login PhotoSwipe Place Blocks Plotly.js Graphing Plupload Poll Popup field group Postoffice Potion Preprocessor Files Preprocessor Plugins Preview graph QL Private DNS Private Message Progressive Web App (PWA) Project Browser Protected Content Pusher API Quadstat Quick Edit Quick Node Clone Quickchat Quicklink RDF RELAXed Web Services RNG Rabbit MQ Radioactivity Range Slider Reactify theme & module Read time Recipes Cookbook Recombee Recurring Dates Field Recurring Events RegEx Field Validation Registration Confirm Email Address Registration codes Registration role Release Version Remote Stream Wrapper Responsive Background Image Responsive Class Field Responsive Image Formatter Tools (RIFT) Responsive Image Preload Responsive Tables Filter Responsive menu Rocket.Chat Integration Module Guide Role paywall Rules Rules API POST SAML Authentication SAML IDP 2.0 Single Sign On (SSO) - SAML Identity Provider SAML SP Single Sign On (SSO) - SAML Service Provider - by Miniorange SMS Framework SMS System SVG Image Field Salesforce ECA Integration Salesforce MFW Salesforce Suite Scheduled Transitions Scheduled Updates Scheduler Schema.org Blueprints Schema.org Metatag Search 404 Search API Search API AI Search API Autocomplete Search API Decoupled Search API Exclude Entity Search API Federated Solr Search API RediSearch Search API Sajari Search API Solr Search API Xunsearch Search API opensolr Search and Replace Scanner SearchStax Search API Select 2 Semantic Views Sender Service Worker Registration Setting up the Release Version module Shared Field Display Settings Sharerich Sherpa Webform ShrinkTheWeb Simple Content Notifications Simple Decoupled Preview Simple FB Connect Simple Instagram Feed Simple Node Importer Simple Page Manager Simple Popup Blocks Simple XML sitemap Simple multi step form Simplenews Single Content Sync Site Module Siteimprove Sitemap Sites Skilling Skins Skosmos Feeds Smart Content Overview Smart Date Smart Title Smart Trim Snippet manager Social API Social Auth Vipps Social Media Platforms Social Migration Social Post Facebook Socialfeed Socialfeed Songkick Sound Management Spectra Analytics Srijan theme Static Node Generator - How to use and Use cases Statistical Spam Filter Statistics Step by step guides to configure various 2FA / MFA / TFA methods Stop Administrator Login String Structure Sync Style Selector Style Switcher Styled Google Map Subgroup Summit Meeting List Superfish Drop-down Menus Swagger UI Field Formatter Swiper Formatter Switches Symfony Mailer Syncer Synonyms System Monitor TMGMT Capita TMGMT Plunet TacJS Tagify Targets Taxonomy Bulk Actions (TBA) Tealium iQ Tag Management Telephone International Widget Template Entities Template Whisperer TextRazor - Automatic text classification The Better Mega Menu Time's Up Token Token Filter Tom Select Tombstones Tone Toolshed Tooltip Tour Transaction Transform API Translation Management Tool Trending Topics Tweet Feed Twig Components Twig Render This Twig Tools Twig tweak Twitter API Block Twitter Tweets Typed Data API Enhancements UI Patterns UI Patterns Pattern Lab UI Styles URL Embed Ubercart Uikit Slideshow Ultimate table Field UniOne Unisender newsletter UpTime Widget Upload File History User CSV Import User Guide for Field Encrypted Searchable - FES User History User Session Management and Monitoring Using CAT tools for Drupal Varbase Editor Varnish purger Vertex AI Search Vertex AI Search Promoted Results Video Video Embed Field Video Toolbox View Transitions Views Add Button Views Bootstrap for Bootstrap 3 Views Bootstrap for Bootstrap 5 Views Bootstrap for Bootstrap4 Views Bulk Operations (VBO) Views Display Union Views Field View Views Local Tasks Views Mobile Views PDF Views RSS: Media (MRSS) Elements Views Reference Field Views Regex Functions Views Remote Data Views Send Views Slideshow Views TimelineJS Views filter content type Vipps Recurring Payments: Installation Visitors Visual Layout Suite Visual Website Optimizer VisualN Visualization Charts Vite Voting API Reaction Wallee Warden Wayfinding Web Page Archive Web Service Data Webform Webform Attachment Gated Download Webform Eloqua Webform GoogleSheets Webform Trello Webform Workflows Element Website Feedback When and why to use Link Param Propagator WissKI WordPress Migrate Wordcount Workbench Menu Access Workflow Workout Usage Workout Usage with Drush Workspace XML Sitemap XML-RPC Xero Sync YAML Content YAML To PHP Youtube Gallery Zoom API agGrid ePayco integration htmLawed HTML filter/purifier memoQ translation miniOrange User Provisioning reCaptcha v3 signageOS simplytest.me Token Configuration Kits Configuration kits are made to make life easier for site builders and module maintainers. This guide will help you use, extend, and create your own configuration kits. Create Your Own Configuration Kit How to export configuration and make your own reusable module Related Content Configuration Kits This project is meant as central registry for modules that act as a configuration kit, or include one or more as a submodule. Guide maintainers Drupal’s online documentation is © 2000-2026 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0 . PHP code is distributed under the GNU General Public License . Infrastructure management for Drupal.org provided by Need a Drupal 7 extended support partner? Consider Tag1. News items News Planet Drupal Social media Sign up for Drupal news Security advisories Jobs Our community Community Services , Training & Hosting Contributor guide Groups & meetups DrupalCon Code of conduct Documentation Documentation Drupal Guide Drupal User Guide Developer docs API.Drupal.org Drupal code base Download & Extend Drupal core Modules Themes Distributions Governance of community About Web accessibility Drupal Association About Drupal.org Terms of service Privacy policy Drupal is a registered trademark of Dries Buytaert . | 2026-01-13T09:29:41 |
https://git-scm.com/book/be/v2/Git-Branching-Branching-Workflows | Git - Branching Workflows About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Першыя крокі 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Падсумаваньне 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Дадатак A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Дадатак B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Дадатак C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 3.4 Git Branching - Branching Workflows Branching Workflows Now that you have the basics of branching and merging down, what can or should you do with them? In this section, we’ll cover some common workflows that this lightweight branching makes possible, so you can decide if you would like to incorporate them into your own development cycle. Long-Running Branches Because Git uses a simple three-way merge, merging from one branch into another multiple times over a long period is generally easy to do. This means you can have several branches that are always open and that you use for different stages of your development cycle; you can merge regularly from some of them into others. Many Git developers have a workflow that embraces this approach, such as having only code that is entirely stable in their master branch — possibly only code that has been or will be released. They have another parallel branch named develop or next that they work from or use to test stability — it isn’t necessarily always stable, but whenever it gets to a stable state, it can be merged into master . It’s used to pull in topic branches (short-lived branches, like your earlier iss53 branch) when they’re ready, to make sure they pass all the tests and don’t introduce bugs. In reality, we’re talking about pointers moving up the line of commits you’re making. The stable branches are farther down the line in your commit history, and the bleeding-edge branches are farther up the history. Малюнак 26. A linear view of progressive-stability branching It’s generally easier to think about them as work silos, where sets of commits graduate to a more stable silo when they’re fully tested. Малюнак 27. A “silo” view of progressive-stability branching You can keep doing this for several levels of stability. Some larger projects also have a proposed or pu (proposed updates) branch that has integrated branches that may not be ready to go into the next or master branch. The idea is that your branches are at various levels of stability; when they reach a more stable level, they’re merged into the branch above them. Again, having multiple long-running branches isn’t necessary, but it’s often helpful, especially when you’re dealing with very large or complex projects. Topic Branches Topic branches, however, are useful in projects of any size. A topic branch is a short-lived branch that you create and use for a single particular feature or related work. This is something you’ve likely never done with a VCS before because it’s generally too expensive to create and merge branches. But in Git it’s common to create, work on, merge, and delete branches several times a day. You saw this in the last section with the iss53 and hotfix branches you created. You did a few commits on them and deleted them directly after merging them into your main branch. This technique allows you to context-switch quickly and completely — because your work is separated into silos where all the changes in that branch have to do with that topic, it’s easier to see what has happened during code review and such. You can keep the changes there for minutes, days, or months, and merge them in when they’re ready, regardless of the order in which they were created or worked on. Consider an example of doing some work (on master ), branching off for an issue ( iss91 ), working on it for a bit, branching off the second branch to try another way of handling the same thing ( iss91v2 ), going back to your master branch and working there for a while, and then branching off there to do some work that you’re not sure is a good idea ( dumbidea branch). Your commit history will look something like this: Малюнак 28. Multiple topic branches Now, let’s say you decide you like the second solution to your issue best ( iss91v2 ); and you showed the dumbidea branch to your coworkers, and it turns out to be genius. You can throw away the original iss91 branch (losing commits C5 and C6 ) and merge in the other two. Your history then looks like this: Малюнак 29. History after merging dumbidea and iss91v2 We will go into more detail about the various possible workflows for your Git project in Distributed Git , so before you decide which branching scheme your next project will use, be sure to read that chapter. It’s important to remember when you’re doing all this that these branches are completely local. When you’re branching and merging, everything is being done only in your Git repository — there is no communication with the server. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:41 |
https://aws.amazon.com/s3/?nc=sn&loc=1#aws-page-content-main | Cloud Object Storage – Amazon S3 – Amazon Web Services Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account Amazon S3 Overview Features Storage classes Pricing Security More Products › Storage › Amazon S3 Amazon S3 Object storage built to retrieve any amount of data from anywhere Sign up What is Amazon S3? Amazon Simple Storage Service (Amazon S3) is an object storage service offering industry-leading scalability, data availability, security, and performance. Millions of customers of all sizes and industries store, manage, analyze, and protect any amount of data for virtually any use case, such as data lakes, cloud-native applications, and mobile apps. With cost-effective storage classes and easy-to-use management features, you can optimize costs, organize and analyze data, and configure fine-tuned access controls to meet specific business and compliance requirements. Play Benefits Scalability You can store virtually any amount of data with S3 all the way to exabytes with unmatched performance. S3 is fully elastic, automatically growing and shrinking as you add and remove data. There’s no need to provision storage, and you pay only for what you use. Durability and availability Amazon S3 provides the most durable storage in the cloud and industry leading availability. Based on its unique architecture, S3 is designed to provide 99.999999999% (11 nines) data durability and 99.99% availability by default, backed by the strongest SLAs in the cloud. Security and data protection Protect your data with unmatched security, data protection, compliance, and access control capabilities. S3 is secure, private, and encrypted by default, and also supports numerous auditing capabilities to monitor access requests to your S3 resources. Lowest price and highest performance S3 delivers multiple storage classes with the best price performance for any workload and automated data lifecycle management, so you can store massive amounts of frequently, infrequently, or rarely accessed data in a cost-efficient way. S3 delivers the resiliency, flexibility, latency, and throughput, to ensure storage never limits performance. Use cases Data lakes Backup and restore data Archive data Generative AI Build a data lake A data lake is a centralized repository that allows you to store all your structured and unstructured data at any scale. You can run data analytics, artificial intelligence (AI), machine learning (ML), and high-performance computing (HPC) applications to unlock the value of your data. With an Amazon S3 data lake, users in Salesforce’s organization can discover, access, and analyze all their data, regardless of where it lives, in a secure and governed way. Read the Salesforce case study Backup and restore critical data Meet your recovery time objective (RTO), recovery point objective (RPO), and compliance requirements with S3's robust replication functionality, data protection with AWS Backup, and various AWS Partner Network solutions. Ancestry uses the Amazon S3 Glacier storage classes to restore terabytes of images in mere hours instead of days. Learn about the Amazon S3 Glacier and S3 Glacier Deep Archive storage classes Archive data at the lowest cost Move data archives to the Amazon S3 Glacier storage classes to lower costs, eliminate operational complexities, and gain new insights. The BBC, a UK public service broadcaster, safely migrated its 100-year-old flagship archive to Amazon S3 Glacier Instant Retrieval. View the BBC case study Put your data to work Because Amazon S3 stores more than 350 trillion objects (exabytes of data) for virtually any use case and averages over 100 million requests per second, it may be the starting point of your generative AI journey. Grendene is creating a generative AI-based virtual assistant for their sales team using a data lake built on Amazon S3. Read the Grendene case study Customers Read more from our customers Industry-leading scalability “Modernizing the NASCAR technology stack by using AWS Storage is an incredibly monumental step in our overall cloud adoption journey at NASCAR. Migrating all our video, audio, and image libraries to the industry-leading scalability, data availability, security, and performance of Amazon S3 allows us to spend more time developing additional workflows that help our business.” — Chris Wolford, Senior Director of Media and Event Technology, NASCAR Read the NASCAR blog Read the NASCAR blog Cost savings “You think about our 400 percent growth, and that translates into user growth and data growth. Amazon S3 is a massively scalable storage service that we use to serve our growing number of customers worldwide. By optimizing our Amazon S3 usage, we can stretch our IT budgets and extend the impact of our technology.” — Manoj Kalyanaraman, Chief Technology Officer, Dropsuite Read the Dropsuite case study Read the Dropsuite case study Preserving history through archives "We want to have a forward-looking strategy, with tools like flexible storage and compute that facilitate the use of machine learning. Our goal is to safeguard the content in the archives so that it’s accessible for another 100 years.” — Brendan Mallon, head of product and services in BBC Archives Technology and Services Read the BBC case study A cornerstone solution “Amazon S3 is the cornerstone of our solution, and it gives us the durability and reliability we need for storing critical data.” — Andre Sublett, Health Cloud, Learning Factory, and Core Services engineer, GE Healthcare Digital Read GE Healthcare Digital case study Read GE Healthcare Digital case study How it works Amazon S3 stores data as objects within buckets. An object is a file and any metadata that describes the file. A bucket is a container for objects. To store your data in Amazon S3, you first create a bucket and specify a bucket name and AWS Region. Then, you upload your data to that bucket as objects in Amazon S3. Each object has a key (or key name), which is the unique identifier for the object within the bucket. S3 provides features that you can configure to support your specific use case. For example, you can use S3 Versioning to keep multiple versions of an object in the same bucket, which allows you to restore objects that are accidentally deleted or overwritten. Buckets and the objects in them are private and can only be accessed with explicitly granted access permissions. You can use bucket policies, AWS Identity and Access Management (IAM) policies, S3 Access Points, and access control lists (ACLs) to manage access. Get started FAQs Amazon S3 FAQs Learn more Getting started Get started with Amazon S3 Start building Free tier Get started with Amazon S3 with AWS Free Tier Sign up Features page Amazon S3 features Learn more Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:41 |
https://www.drupal.org/docs/contributed-modules/configuration-kits#block-system-main-menu | Configuration Kits | Contributed module documentation | Drupal Wiki guide on Drupal.org Skip to main content Skip to search Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see ? Yes, please No, do not track me Drupal.org home Discover Drupal Drupal Core Drupal CMS Drupal AI Case Studies Drupal for Government Drupal for Higher Education Drupal for Nonprofit Drupal for eCommerce Drupal for FinTech Drupal for Healthcare Drupal for Enterprise Drupal for Retail Drupal for Travel & Tourism Build with Drupal Download Drupal Documentation Getting started Local Development Guide Developer Resources Drupal CMS User Guide Drupal User Guide API Modules Themes Distributions Issue queues Security Advisories Partners & Services Find a Drupal Certified Partner Become a Drupal Certified Partner Find a Hosting Provider Find a Migration Partner Find Training Drupal Steward Community About the Community How to Contribute DrupalCon Events Jobs / Careers News & Blogs Forum Slack Newsletters Drupal Swag Shop Support Drupal The Drupal Association Donate Become a Partner Become a Ripple Maker Become an Organization Member Drupal Swag Shop Get Started Try Drupal CMS Try Hosting Return to content Search form Search Log in Create account Documentation Search Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options. Migration Resource Center Drupal Extending Drupal Contributed modules Contributed module documentation Advertising sustains the DA. Ads are hidden for members. Join today Contributed module documentation Active Tags A11Y Paragraphs Tabs AI AI Interpolator AI Migration API Authentication API module APITools Accelerated Mobile Pages (AMP) Access NASA API Access Policy Accessibility Scanner Acquia Migrate: Accelerate Actions UI Activity Tracker module ActivityPub Add To Calendar Date Augmenter AddToAny Share Buttons Address Decoupled Address for Luxembourg Address for Rep. of Moldova Admin Menu Swap Adobe Launch Advanced CSS/JS Aggregation Advanced Email Validation Advanced File Destination - Ho to use Advanced Insert View Advanced Varnish Advanced Views RSS Feed Aggregator Akamai Album Photos Alexa Allow a content type only once (Only One) Altcha Anu LMS Apigee API Catalog Apigee Developer Portal Kickstart Apigee Edge Apigee Monetization Apple News Astrology Atoms AudioField Audit files Augmentor User Guide Authorization Auto Link Auto Node Translate Auto Taxonomy Term Translate AutoFloat Automatic Updates Avatar Kit Azure Drupal Sync BAT Guide BEE hotel Backstop Generator Backup and Migrate Bamboo Twig Barcodes Behat UI Better Exposed Filters Bibliography & Citation BigCommerce Block Class Block Form Alter Block List Override Block Style Plugins Blog Book Boost Bootstrap Layouts Bootstrap Paragraphs Bootstrap Quick Tabs Bootstrap Theme Toggler Block Bothive Chatbot Botman Boxout Braintree Cashier Breakgen Brightcove Video Connect Bundle override Burndown Business Rules Bynder CAS CDEK API CKEditor 4 LTS CKEditor 5 Premium Features CKEditor CKEditor Accessibility Auditor CKEditor CodeMirror CKEditor Entity Link CKEditor Font Size and Family CKEditor Google Search CKEditor Libraries Group CKEditor: N1ED plugin CMRF Core Documentation CSV Importer CSV to Config Cached moderation state Calendar View Canvas LTI Captcha Keypad Changed Fields API (8.x-3.x) Changed Fields API Chaos Tool Suite (ctools) Chart Suite Guide Charts Chatbot API Chatbot Framework Claro Cloud Cloudflare Stream Cloudinary Coder Collapsiblock Color Color Field Comment Notify Comment mover Commerce Commerce API Commerce Affirm Credit Payment Gateway Commerce Approve Commerce Authorize.Net Commerce Braintree Commerce Cart API Commerce Cart Flyout Commerce DIBS integration Commerce Easy Commerce Funds Commerce Google Tag Manager Commerce Ingenico Commerce Inventory Commerce Invoice Commerce Migrate Commerce NoFraud Commerce Order Document Commerce PVT Commerce Pagseguro Transparente Commerce PayPal Commerce Payment Extra Commerce Point of Sale (POS) Commerce PostFinance Checkout Commerce Postfinance Commerce Product Options Commerce Recurring Metered Commerce Rental Commerce Reporting Commerce Square Connect Commerce Time Slots Commerce Tpay Commerce TrustedShops Commerce Variation Add-on Commerce Webform Order Commerce iATS Commerce iDEAL Payment Gateway Component Schema Components Computed Field Computed Field Plugin Conditional Fields Config Override Inspector Config Pages Config Single Export Config Token Config partial export Configuration Kits Configuration Split Content Alerts Content Feedback Content Import Content Packager Content Planner Content Synchronization Content-Security-Policy ContentAccess Create fields programmatically Crossword CrowdSec CsvtoTable Cura Childcare Suite Cura Childcare Suite Currency Custom 4XX Pages Custom API Custom Field Custom Status Report Custom Tokens Custom Tokens and its snippets Custom breadcrumbs Customerror D8 Rules Essentials Dashboard Date Augmenter API Decoupled Blocks: Vue.js Decoupled Toolbox Decoupled Toolbox Decoupled quiz Default Content for D8 Delete Entity Translations Dempo Deploy Deploying Meilisearch to production Devel Devel Generate Commerce Developer Suite Developer portal Digital Signage Framework Disclosure Menu Disclosure Menu Display Suite Chained Fields Dominican Catalogus Module DraggableViews Drupal Chatbot Drupal Commerce Merchant Warrior Drupal Contribution Drupal Diversity & Inclusion Drupal Js Path Drupal LMS Drupal OAuth & OpenID Connect Login - OAuth2 Client SSO Login Drupal OAuth OIDC Login Drupal Remote Dashboard Drupal Slider Drupal Website Security – Complete Protection for Your Site Drupal WhatsApp Drupal YouTuber Drupal driver for SQL Server and SQL Azure DubBot ECA: Event - Condition - Action ECC EU Cookie Compliance EVA Easy Breadcrumb Easy News Editor Button Link Ek Jitsi Elasticsearch Connector Email Verification / SMS Verification / OTP Verification Encrypt Entitree Administration Guide Entity Access Password Entity Browser - Table Layout Entity Browser Entity Pager Entity Parser Entity Prepopulate Entity Print Entity Reference Facet Link Entity Reference Override Entity Reference Views Entity Reference Views Select Entity Registration Entity Search Autoindex Entity Share Entity Share WebSub Entity Update Entity Usage Entity Usage Addons Entity browser Environment indicator Epsilon Harmony Connector Ethereum Evaluate Webform Event Platform Events Logger Excel Importer Exerciser Usage Expire reset password link Extensions API External Authentication External Entities External Entities Database storage Extra Block Types (EBT) Extra Paragraph Types (EPT) Facebook Instant Articles Facet Bot Blocker Facets Facets Date Range Picker Factory Lollipop Feature Toggle Features Feeds Feeds Migrate Feeds Paragraphs Feeds extensible parsers Field Encrypt Field Gallery Field Group Field Inheritance Field description tooltip Field validation File Extractor Filebrowser FillPDF Firebase Authentication Guide Fivestar Flag Flag Lists Flashpoint Education Flexible Views Flickr Integration Suite Flow2 Fluent Flysystem Focal Point Focal Point FolderShare Guide Font Awesome Icons Footnotes Form mode manager FormAlter as Plugin FormAssembly Formatter Suite Guide Formdazzle! Forms steps FortyTwo Forum module Forward Freelinking Frontend Editing Frontify Assets FullCalendar Block Funding GA Push GIT Info Report GLightbox Gatsby Integration General Data Protection Regulation Geocluster D8/D9 Set-up Geofield Geolocation Field Get Linkedin Posts Ghost Inspector Integrator Ghost Inspector Integrator Gin Toolbar Custom Menu Ginger Robot Gardens Ginger Robot Suite Give GlobalDoc’s LangXpert Connect for Drupal Googalytics Google API PHP Client Google Analytics Google Analytics Counter Google Analytics Search API Autocomplete Google Authentication for Users Google Bard Google Calendar Import Google Programmable Search Engine Gophish Integration GovUK Notify GrapesJs Editor - Page builder GraphQL Grid Widget Group Group Content Moderation Group Flex Group Invite Group Media Group Subscription Group by Field Widget Grouper Usage Gutenberg Gutenberg Content Embed Gutenberg Starter Gutenberg Starter Gutenberg USWDS Guzzle REST Generator HAL HAX HTML Mail HTML Title HTTP Client Manager Hanging Conjunctions Filter HelloSign Hidden Tab Honeypot Hospital Price Transparency Hotkeys for Save How to Configure Drupal Sharepoint Integration How to test a module locally using DDEV (Webform Booking example) Human Presence Form Protection Hux IMCE File Manager IPMA Weather Iconify Icons If Then Else Iframe Media Embed Video Image Base64 Formatter Image Optimize Image Replace Imageshop Immoweb API Client In Other Words Inline Formatter Field Insert Instagram Block Integrating Frontify with Drupal: A Comprehensive Guide Intercept Islandora JSON Field Utils JSON:API Search API Janrain Connect Juicebox HTML5 Responsive Image Galleries Juicer - Social Media Feed Aggregator Key Keycloak OpenID Connect Klaro Consent Management Knowledge Konami Code LDAP Integration LDAP Integration with Active Directory and OpenLDAP - NTLM & Kerberos Login Language Negotiation Url Matrix Layout BG Layout Builder Additions Layout Builder Block Sanitizer Layout Builder Plus Layout Builder Restrictions Layout Builder Settings Report Layout Builder Styles Layout Builder Tabs Section Layout Components Layout Options Layout Paragraphs Lazy-load Leaflet Leaflet More Markers Libraries API LiftIgniter Lightgallery Lightning Accessibility Lightweight Directory Access Protocol (LDAP) Link attributes Link icon Linkback Linkit Lndr Localist Drupal Localization server Localized Configuration Loco Translate Loqate Ludwig Lunr search Maestro Maestro Activepieces Integration Mailchimp Maintenance Manage display Managing User Account Expiration with User Expire Module Mapbox Field Markdown Markdown Easy Markdown Exporter Marketing Cloud Mask Field Matomo Analytics Maxlength Media Contextual Crop Media Gallery Media Library Form Element Media PDF Thumbnail Media Video Micromodal Media: Acquia DAM Membership Menu Manipulator Menu Migration (Import & Export) Message Message Integration Message Thread Metatag Metatag Google Scholar Micro Site Microsoft Entra ID SSO Login Microsoft Entra sync Migrate Magician Migrate QA Migrate Source CSV Migrate Source GraphQL Migrate Source JCR Migration Tools Mime Mail Mix Modal Modifiers Moodle REST Mother May I Multilanguage Form Display Multiple Registration Multistep Form Framework Multiversion NASA Astronomy Picture of the Day NFT Name Field Nbox Node Type count Notify OAuth 1.0 OAuth Server - API Documentation OAuth Server - SSO Setup Guides OAuth2 & OpenID Connect OAuth2 Client OEmbed Lazyload OH Office 365 Connector One Time Password SMS Open ReadSpeaker OpenChurch OpenEDU OpenID Connect OpenID Connect Microsoft Azure Active Directory client OpenLayersD8 OpenQuestions Openlayers Oracle Driver Oracle Eloqua API Redux OwnTracks PCO - Planning Center Online API PHP filter PNX Gallery PNX Media Packages Packagist Pagedesigner Panopoly 2 for Drupal 8/9 Paragraph Group Paragraphs Paragraphs Bundles Paragraphs Bundles Import Paragraphs Collection Paragraphs Gridstack Paragraphs Role Visibility Parameter Message Paranoia Pathauto Patternkit Performance Budget Permalink Block Permanent Entities Permissions by Term Persistent Login PhotoSwipe Place Blocks Plotly.js Graphing Plupload Poll Popup field group Postoffice Potion Preprocessor Files Preprocessor Plugins Preview graph QL Private DNS Private Message Progressive Web App (PWA) Project Browser Protected Content Pusher API Quadstat Quick Edit Quick Node Clone Quickchat Quicklink RDF RELAXed Web Services RNG Rabbit MQ Radioactivity Range Slider Reactify theme & module Read time Recipes Cookbook Recombee Recurring Dates Field Recurring Events RegEx Field Validation Registration Confirm Email Address Registration codes Registration role Release Version Remote Stream Wrapper Responsive Background Image Responsive Class Field Responsive Image Formatter Tools (RIFT) Responsive Image Preload Responsive Tables Filter Responsive menu Rocket.Chat Integration Module Guide Role paywall Rules Rules API POST SAML Authentication SAML IDP 2.0 Single Sign On (SSO) - SAML Identity Provider SAML SP Single Sign On (SSO) - SAML Service Provider - by Miniorange SMS Framework SMS System SVG Image Field Salesforce ECA Integration Salesforce MFW Salesforce Suite Scheduled Transitions Scheduled Updates Scheduler Schema.org Blueprints Schema.org Metatag Search 404 Search API Search API AI Search API Autocomplete Search API Decoupled Search API Exclude Entity Search API Federated Solr Search API RediSearch Search API Sajari Search API Solr Search API Xunsearch Search API opensolr Search and Replace Scanner SearchStax Search API Select 2 Semantic Views Sender Service Worker Registration Setting up the Release Version module Shared Field Display Settings Sharerich Sherpa Webform ShrinkTheWeb Simple Content Notifications Simple Decoupled Preview Simple FB Connect Simple Instagram Feed Simple Node Importer Simple Page Manager Simple Popup Blocks Simple XML sitemap Simple multi step form Simplenews Single Content Sync Site Module Siteimprove Sitemap Sites Skilling Skins Skosmos Feeds Smart Content Overview Smart Date Smart Title Smart Trim Snippet manager Social API Social Auth Vipps Social Media Platforms Social Migration Social Post Facebook Socialfeed Socialfeed Songkick Sound Management Spectra Analytics Srijan theme Static Node Generator - How to use and Use cases Statistical Spam Filter Statistics Step by step guides to configure various 2FA / MFA / TFA methods Stop Administrator Login String Structure Sync Style Selector Style Switcher Styled Google Map Subgroup Summit Meeting List Superfish Drop-down Menus Swagger UI Field Formatter Swiper Formatter Switches Symfony Mailer Syncer Synonyms System Monitor TMGMT Capita TMGMT Plunet TacJS Tagify Targets Taxonomy Bulk Actions (TBA) Tealium iQ Tag Management Telephone International Widget Template Entities Template Whisperer TextRazor - Automatic text classification The Better Mega Menu Time's Up Token Token Filter Tom Select Tombstones Tone Toolshed Tooltip Tour Transaction Transform API Translation Management Tool Trending Topics Tweet Feed Twig Components Twig Render This Twig Tools Twig tweak Twitter API Block Twitter Tweets Typed Data API Enhancements UI Patterns UI Patterns Pattern Lab UI Styles URL Embed Ubercart Uikit Slideshow Ultimate table Field UniOne Unisender newsletter UpTime Widget Upload File History User CSV Import User Guide for Field Encrypted Searchable - FES User History User Session Management and Monitoring Using CAT tools for Drupal Varbase Editor Varnish purger Vertex AI Search Vertex AI Search Promoted Results Video Video Embed Field Video Toolbox View Transitions Views Add Button Views Bootstrap for Bootstrap 3 Views Bootstrap for Bootstrap 5 Views Bootstrap for Bootstrap4 Views Bulk Operations (VBO) Views Display Union Views Field View Views Local Tasks Views Mobile Views PDF Views RSS: Media (MRSS) Elements Views Reference Field Views Regex Functions Views Remote Data Views Send Views Slideshow Views TimelineJS Views filter content type Vipps Recurring Payments: Installation Visitors Visual Layout Suite Visual Website Optimizer VisualN Visualization Charts Vite Voting API Reaction Wallee Warden Wayfinding Web Page Archive Web Service Data Webform Webform Attachment Gated Download Webform Eloqua Webform GoogleSheets Webform Trello Webform Workflows Element Website Feedback When and why to use Link Param Propagator WissKI WordPress Migrate Wordcount Workbench Menu Access Workflow Workout Usage Workout Usage with Drush Workspace XML Sitemap XML-RPC Xero Sync YAML Content YAML To PHP Youtube Gallery Zoom API agGrid ePayco integration htmLawed HTML filter/purifier memoQ translation miniOrange User Provisioning reCaptcha v3 signageOS simplytest.me Token Configuration Kits Configuration kits are made to make life easier for site builders and module maintainers. This guide will help you use, extend, and create your own configuration kits. Create Your Own Configuration Kit How to export configuration and make your own reusable module Related Content Configuration Kits This project is meant as central registry for modules that act as a configuration kit, or include one or more as a submodule. Guide maintainers Drupal’s online documentation is © 2000-2026 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0 . PHP code is distributed under the GNU General Public License . Infrastructure management for Drupal.org provided by Need a Drupal 7 extended support partner? Consider Tag1. News items News Planet Drupal Social media Sign up for Drupal news Security advisories Jobs Our community Community Services , Training & Hosting Contributor guide Groups & meetups DrupalCon Code of conduct Documentation Documentation Drupal Guide Drupal User Guide Developer docs API.Drupal.org Drupal code base Download & Extend Drupal core Modules Themes Distributions Governance of community About Web accessibility Drupal Association About Drupal.org Terms of service Privacy policy Drupal is a registered trademark of Dries Buytaert . | 2026-01-13T09:29:41 |
https://aws.amazon.com/getting-started/onboarding-to-aws/ | Onboarding to AWS Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account Getting Started Resource Center Get Started Learn Get Connected Developer Tools More Resources More Getting Started › Onboarding to AWS Onboarding to AWS If you're a beginner looking for a starting point to learn AWS, we recommend that you complete the following six onboarding tasks. These tasks will help you learn how to launch and configure several different AWS services across a broad range of categories. Sign in Choose a task Task 1 Launch compute resources Learn more Task 2 Create storage resources Learn more Task 3 Create database resources Learn more Task 4 Deploy an application Learn more Task 5 Set up monitoring Learn more Task 6 Set up cost monitoring Learn more Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:41 |
https://support.smartbear.com/reflect/docs/en/index-en.html | Reflect Documentation | Reflect Documentation Skip to main content Support Toggle navigation How can we help you today? Overview How to Track Usage Recording Manage Tests API Integrations Release Notes Reflect Tunnel Featured content 5 Overview Quick Start Tests You Should Create Test Generative AI Apps and Agents Account Setup 1 How to Track Usage 13 Recording Create Resilient Tests Test with AI Reflect Mobile Supported Actions Testing Visual State Variables & Parameters Segments & Composition API Testing Email / SMS Testing Private Environments Local Testing Automating Manual Tests Show more... Show less... 5 Manage Tests View Test Run Editing / Re-Recording Folders Suites Search results No results found © 2025 English English Contact us USA +1 617-684-2600 EUR +353 91 398300 AUS +61 391929960 Company About Careers Contact Us Newsroom Partners Responsibility Resources Academy Community Resource Center Support Products Swagger BugSnag TestComplete ReadyAPI Zephyr Enterprise View All Products Legal Privacy Security Terms of Use Website Terms of Use Facebook Instagram Linkedin X YouTube © 2025 SmartBear Software. All Rights Reserved. | 2026-01-13T09:29:41 |
https://support.microsoft.com/tr-tr/microsoft-store-and-billing | Microsoft Store ve faturalama yardımı Ana içeriğe atla Microsoft Destek Destek Destek Giriş Microsoft 365 Office Ürünler Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows diğer ... Cihazlar Surface Bilgisayar Donatıları Xbox Bilgisayar Oyunları HoloLens Surface Hub Donanım garantileri Hesap ve faturalandırma Hesap Microsoft Store ve faturalama Kaynaklar Yenilikler Topluluk forumları Microsoft 365 Yöneticileri Küçük İşletme Portalı Geliştirici Eğitim Destek dolandırıcılığını bildirin Ürün güvenliği Daha fazla Microsoft 365’i satın alın Tüm Microsoft Global Microsoft 365 Teams Copilot Windows Xbox Destek Yazılım Yazılım Windows Uygulamaları Yapay Zeka OneDrive Outlook Skype'tan Teams'e geçiş yapma OneNote Microsoft Teams PCs ve cihazlar PCs ve cihazlar Xbox alın Aksesuarları Eğlence Eğlence Xbox Game Pass Ultimate Xbox ve oyunlar PC Oyunları İş İş Microsoft Güvenlik Azure Dynamics 365 İş için Microsoft 365 Microsoft Industry Microsoft Power Platform Windows 365 Geliştirici ve BT Geliştirici ve BT Microsoft Geliştiricisi Microsoft Learn Yapay zeka market uygulamaları için destek Microsoft Tech Community Microsoft Marketplace Visual Studio Marketplace Rewards Diğer Diğer Ücretsiz yüklemeler ve güvenlik Eğitim Site Haritasını Göster Ara Yardım arayın Sonuç yok İptal Oturum aç Microsoft hesabıyla oturum açın Oturum açın veya hesap oluşturun. Merhaba, Farklı bir hesap seçin. Birden çok hesabınız var Oturum açmak istediğiniz hesabı seçin. Microsoft Store ve faturalama yardımı Abonelikleri yönetme para iadelerini & verir Ödeme seçenekleri Sipariş geçmişi Hediye kartları Microsoft 365'i yükleme Windows'ta Microsoft Store Microsoft Store hizmetlerini keşfedin Ücretsiz gönderimden 60 günlük fiyat korumamıza kadar sınıfının en iyisi cihazlar, yazılımlar, oyunlar ve kaynaklarla daha fazlasını yapmanıza yardımcı olmak için buradayız. Microsoft Store'un sunduğu avantajlara göz atın: Alışveriş ve satın alma desteği | Ürün kurulumu ve eğitimi | Küçük işletme desteği Alışveriş ve satın alma desteği Microsoft Store hizmetleri tüm bölgelerde kullanılamaz. Kullanabileceğiniz seçenekleri görmek için aşağıdaki açılan listeden ülkenizi veya bölgenizi seçin ve listede yoksa Diğer bölgeler . Bölgenizi seçin ABD Avustralya Kanada (İngilizce) Kanada (Fransızca) Birleşik Krallık Diğer bölgeler Neden Microsoft Store'da alışveriş yapın? Kolay, kullanışlı alışveriş Ücretsiz 2-3 gün gönderim 60 günlük ücretsiz iadeler 60 günlük fiyat koruması Esnek ödeme seçenekleri Kullandığınız cihaz için nakit Takas ve geri dönüşüm Özel indirimler ve teklifler Öğrenciler, ebeveynler ve eğitimciler için Askeri personel için Genişletilmiş cihaz koruması Microsoft Complete koruma planı İhtiyacınız olanı bulmanıza yardımcı olabilir Satış desteği yardımı Engellilik için yardım masası ASL iş ortağıyla alışveriş yapma Neden Microsoft Store'da alışveriş yapın? Kolay, kullanışlı alışveriş Ücretsiz gönderim 60 günlük ücretsiz iadeler 60 günlük fiyat koruması Kullandığınız cihaz için nakit Takas ve geri dönüşüm Özel indirimler ve teklifler Öğrenciler, ebeveynler ve eğitimciler için İhtiyacınız olanı bulmanıza yardımcı olabilir Satış desteği yardımı Engellilik için yardım masası Neden Microsoft Store'da alışveriş yapın? Kolay, kullanışlı alışveriş Ücretsiz gönderim 60 günlük ücretsiz iadeler 60 günlük fiyat koruması Kullandığınız cihaz için nakit Takas ve geri dönüşüm Özel indirimler ve teklifler Öğrenciler, ebeveynler ve eğitimciler için Genişletilmiş cihaz koruması Microsoft Complete koruma planı İhtiyacınız olanı bulmanıza yardımcı olabilir Satın almadan önce sorularınız varsa bir ürün uzmanıyla sohbet edin veya alışveriş randevusu alın. Satış desteği yardımı Neden Microsoft Store'da alışveriş yapın? Kolay, kullanışlı alışveriş Ücretsiz gönderim 60 günlük ücretsiz iadeler 60 günlük fiyat koruması Kullandığınız cihaz için nakit Takas ve geri dönüşüm Özel indirimler ve teklifler Öğrenciler, ebeveynler ve eğitimciler için Genişletilmiş cihaz koruması Microsoft Complete koruma planı Neden Microsoft Store'da alışveriş yapın? Kolay, kullanışlı alışveriş Ücretsiz gönderim 60 günlük ücretsiz iadeler 60 günlük fiyat koruması Kullandığınız cihaz için nakit Takas ve geri dönüşüm Özel indirimler ve teklifler Öğrenciler, ebeveynler ve eğitimciler için İhtiyacınız olanı bulmanıza yardımcı olabilir Satış desteği yardımı Engellilik için yardım masası Neden Microsoft Store'da alışveriş yapın? İhtiyacınız olanı bulmanıza yardımcı olabilir Satın almadan önce sorularınız varsa bir ürün uzmanıyla sohbet edin. Satış desteği yardımı Microsoft Store'a göz atın The Microsoft Store Ürün kurulumu ve eğitimi Burada listelenen tüm Microsoft Store hizmetleri tüm bölgelerde kullanılamaz. Seçeneklerinizi görmek için aşağıdaki açılan listeden ülkenizi veya bölgenizi seçin: Bölgenizi seçin ABD Avustralya Kanada (İngilizce) Kanada (Fransızca) Birleşik Krallık Diğer bölgeler Yardım ve öğrenme kaynakları İhtiyacınız olan yanıtları bulmanıza yardımcı olması için ürün destek kaynaklarımızı gözden geçirin. Surface cihazları | Xbox Microsoft 365 | Windows Yardım ve öğrenme kaynakları Ürün destek kaynaklarımız, ihtiyacınız olan yanıtları bulmanıza yardımcı olmak için buradadır. Surface cihazları | Xbox Microsoft 365 | Windows Yardım ve öğrenme kaynakları İhtiyacınız olan yanıtları bulmanıza yardımcı olması için ürün destek kaynaklarımızı gözden geçirin. Surface cihazları | Xbox Microsoft 365 | Windows Yardım ve öğrenme kaynakları İhtiyacınız olan yanıtları bulmanıza yardımcı olması için ürün destek kaynaklarımızı gözden geçirin. Surface cihazları | Xbox Microsoft 365 | Windows Yardım ve öğrenme kaynakları İhtiyacınız olan yanıtları bulmanıza yardımcı olması için ürün destek kaynaklarımızı gözden geçirin. Surface cihazları | Xbox Microsoft 365 | Windows Yardım ve öğrenme kaynakları İhtiyacınız olan yanıtları bulmanıza yardımcı olması için ürün destek kaynaklarımızı gözden geçirin. Surface cihazları | Xbox Microsoft 365 | Windows Küçük işletme desteği Bölgenizde hangi küçük işletme destek seçeneklerinin kullanılabildiğini görmek için aşağıdaki açılan listeden ülkenizi veya bölgenizi seçin: Bölgenizi seçin ABD Avustralya Kanada (İngilizce) Kanada (Fransızca) Birleşik Krallık Diğer bölgeler Küçük işletmeniz için kaynaklar İşletmenizin gelişmesine yardımcı olacak tavsiyeler, ücretsiz eğitimler, ürünler ve araçlar alın. Küçük işletme yardımı ve öğrenme Küçük İşletme Kaynak Merkezi Küçük işletmeniz için kaynaklar İşletmenizin gelişmesine yardımcı olacak tavsiyeler, ücretsiz eğitimler, ürünler ve araçlar alın. Küçük işletme yardımı ve öğrenme Küçük İşletme Kaynak Merkezi Küçük işletmeniz için kaynaklar İşletmenizin gelişmesine yardımcı olacak tavsiyeler, ücretsiz eğitimler, ürünler ve araçlar alın. Küçük işletme yardımı ve öğrenme Küçük işletme kaynak merkezi Küçük işletmeniz için kaynaklar İşletmenizin gereksinimlerini değerlendirmeden kurulum ve sorun giderme konusunda yardımcı olmak için buradayız. İşletmenizin gelişmesine yardımcı olacak tavsiyeler, ücretsiz eğitimler, ürünler ve araçlar alın. Küçük işletme yardımı ve öğrenme Küçük işletme kaynak merkezi Küçük işletmeniz için kaynaklar İşletmenizin gelişmesine yardımcı olacak tavsiyeler, ücretsiz eğitimler, ürünler ve araçlar alın. Küçük işletme yardımı ve öğrenme Küçük İşletme Kaynak Merkezi Küçük işletmeniz için kaynaklar İşletmenizin gelişmesine yardımcı olacak tavsiyeler, ücretsiz eğitimler, ürünler ve araçlar alın. Küçük işletme yardımı ve öğrenme Yenilikler Kuruluşlar için Copilot Kişisel kullanım için Copilot Microsoft 365 Microsoft ürünlerini keşfedin Windows 11 uygulamaları Microsoft Store Hesap profili İndirme Merkezi Microsoft Store Desteği İadeler Sipariş izleme Eğitim Microsoft Eğitim Eğitim cihazları Eğitim için Microsoft Teams Microsoft 365 Eğitim Office Eğitimi Eğitimci eğitimi ve gelişimi Öğrenciler ve ebeveynler için fırsatlar Öğrenciler için Azure İşletme Microsoft Güvenlik Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Geliştirici ve BT Microsoft Geliştiricisi Microsoft Learn Yapay zeka market uygulamaları için destek Microsoft Tech Community Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Şirket Kariyer Fırsatları Microsoft Hakkında Microsoft'ta Gizlilik Yatırımcılar Sürdürülebilirlik Türkçe (Türkiye) Gizlilik Tercihleriniz Geri Çevirme Simgesi Gizlilik Tercihleriniz Gizlilik Tercihleriniz Geri Çevirme Simgesi Gizlilik Tercihleriniz Tüketici Durumu Gizliliği Microsoft'a başvurun Gizlilik Tanımlama bilgilerini yönetin Kullanım Şartları Ticari Markalar Reklamlarımız hakkında © Microsoft 2026 | 2026-01-13T09:29:41 |
https://dsf.berkeley.edu/ | Berkeley Data Systems and Foundations (DSF) Group UC BERKELEY DATA SYSTEMS AND FOUNDATIONS Berkeley has been a leader in data systems research through 50 years of evolution. As data has become increasingly central to computing and society, our group's charter and collaborations have expanded. Our research covers a wide range of topics in data-centric computing. This includes projections on database systems, distributed systems, human computing and interaction, programming languages, security and privacy, AI and machine learning systems, and the theory of computation. We actively support Berkeley's Principles of Community , recognizing the intrinsic relationship between diversity and excellence in all our endeavors. NEWS --> Berkeley campus press release, 2019 including selected faculty profiles --> There are a number of ongoing projects in the group, such as Hydro . DSF faculty are also part of the EPIC , Sky , and Slice labs so be sure to check out projects listed there! COORDINATING FACULTY Alvin Cheung Natacha Crooks Joseph Gonzalez Joe Hellerstein Aditya Parameswaran AFFILIATED FACULTY Ali Ghodsi Michael Jordan Jelani Nelson Raluca Popa Ion Stoica Matei Zaharia GRADUATE STUDENTS Nithin Chalapathi Audrey Cheng David Chu Chris Douglas Rolando Garcia Neil Giridharan Mick Kittivorawong Shadaj Laddad Xiaoxuan (Lily) Liu Conor Power Johann Schleier-Smith Shreya Shankar Samyu Yagati Zongheng Yang POST-DOCTORAL FELLOWS Tiemo Bang Suyash Gupta Mae Milano Dixin Tang RECENT ALUMNI Sameer Agarwal Sara Alspaugh Peter Alvaro Peter Bailis Daniel Bruckner Saurav Chhatrapati Daniel Crankshaw Neil Conway Anusha Dandamudi Daniel Haas Tomer Kaftan Christos Kozanitis Tim Kraska Sanjay Krishnan Erik Krogen Nick Lanham Doris Jung-Lin Lee Charles Lin Eric Liu Gene Pang Devin Petersohn Josh Rosen Mingwei Samuel Vikram Sreekanti Liwen Sun Ameet Talkwalkar Beth Trushkowsky Shivaram Venkataraman Jiannan Wang Xin Wang Michael Whittaker Chenggang Wu Yifan Wu Doris Xin Reynold Xin Larry Xu ACTIVITY BEYOND BERKELEY Alumni have taken faculty positions at: Cal State Stanislaus Cornell Harvard Harvey Mudd IIT Bombay MIT Maryland Stanford U Chicago U Florida UBC UC Berkeley UC Irvine UC Santa Cruz UCLA UMass Amherst UPenn Wisconsin Alumni have taken research and leadership positions at: Startups founded by faculty and alumni: | 2026-01-13T09:29:41 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.